plungeai_list_agents

Read-onlyCreates an execution: no

https://mcp.plungeai.com/v1tools/callplungeai_list_agents

Authorizations

Authorizationstringheader

Bearer token: Authorization: Bearer ozk_….

X-API-Keystringheader

Alternative header: X-API-Key: ozk_….

Every request needs a key, tools/list included.

Arguments

user_requeststring

The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.

Maximum string length: 4000

searchstring

Maximum string length: 2000

categorystring

Maximum string length: 256

agent_idstring

Maximum string length: 256

kindenum<string>

Available options: agents, personas, experts, skills, models, workflows, connectors

Default: agents

limitinteger

Default: 25 with search or category, 100 without

Required range: 1 <= x <= 100

formatenum<string>

markdown (default): rendered for an AI reader · json: the same outcome as a JSON document in text plus structuredContent

Available options: markdown, json

Default: markdown

Output

Markdown text; format: "json" returns the same answer as a JSON document.

Discover platform building-block agents from the live registry (the capability catalog). NOT the user's own agents — for "show me my agents/workflows" use plungeai_list_workflows. search is a hybrid semantic+keyword query — describe the capability in natural language (e.g. "web search", "pdf to markdown"). Prefer search/category filters; an unfiltered list returns the whole catalog (~90 agents, large). The catalog is active-only, and execution refuses any id that is not active — so take ids from here, not from memory. Fetch one full card with agent_id. With format: "json" the result is {content: <markdown>} — its source is rendered registry markdown; typed rows are a follow-up.

Discover platform building-block agents in the live registry, the capability catalog. These are registry agents, not the user's own agents: for "show me my agents / workflows" use plungeai_list_workflows. search is a hybrid semantic and keyword query: describe the capability in natural language (for example "web search", "pdf to markdown"). Prefer search / category filters; an unfiltered list returns the whole catalog (about 90 agents, large). The catalog is active-only and execution refuses any id that is not active, so take ids from here, not from memory. Fetch one full card with agent_id. With format:"json" the result is {content: <markdown>}: its source is rendered registry markdown, and typed rows are a follow-up.

Returns. Registry Markdown: the matching cards, or one full card for agent_id. The active-only filter applies to kind: "agents". An agent_id that does not exist, or is not active, gets an explanation and the closest live matches instead of the card. Registry unavailable — try again shortly. (isError: true) when the registry does not answer.

curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_list_agents","arguments":{"user_request":"which agents can search the web?","search":"web search"}}}'

Two parameters recur across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it) and format (markdown by default, or json). Both are described once in Recurring parameters on the MCP overview.

import json import os import requests response = requests.post( "https://mcp.plungeai.com/v1", headers={ "Authorization": f"Bearer {os.environ['PLUNGE_API_KEY']}", "Accept": "application/json, text/event-stream", "Content-Type": "application/json", }, json={ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "plungeai_list_agents", "arguments": {}, }, }, ) for line in response.text.splitlines(): if line.startswith("data: "): print(json.loads(line[6:]))

import { Client } from '@modelcontextprotocol/sdk/client/index.js' import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js' const transport = new StreamableHTTPClientTransport(new URL('https://mcp.plungeai.com/v1'), { requestInit: { headers: { Authorization: `Bearer ${process.env.PLUNGE_API_KEY}` } }, }) const client = new Client({ name: 'my-app', version: '1.0.0' }) await client.connect(transport) const result = await client.callTool({ name: 'plungeai_list_agents', arguments: {} }) console.log(result.content)

curl -N -X POST 'https://mcp.plungeai.com/v1' \ -H "Authorization: Bearer $PLUNGE_API_KEY" \ -H 'Accept: application/json, text/event-stream' \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_list_agents","arguments":{}}}'

plungeai_list_agents

Authorizations

Arguments

Output

Planned: TI-33

Planned: TI-34