resources/read - PlungeAI

Reads one resource or template instance. Support: supported.

Params

Param	Type	Required	Description
`uri`	string	yes	A static URI or a filled-in template, for example `plungeai://agents/categories`

Result

Field	Value
`contents[]`	One entry: `{ "uri", "mimeType", "text" }`

Example

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":6,"method":"resources/read","params":{"uri":"plungeai://agents/categories"}}'

{"jsonrpc":"2.0","id":6,"result":{"contents":[{"uri":"plungeai://agents/categories","mimeType":"text/markdown","text":"…"}]}}

The response above is abridged: the resource's Markdown text is shortened to ….

Errors

Protocol errors mean the request never reached a tool; the body is {"jsonrpc":"2.0","error":{"code":…,"message":"…"},"id":…}.

HTTP	Code	When
200	`-32002`	`MCP error -32002: Resource not found: <uri>`; also `Workflow not found` and `Execution not found` for the two id templates
200	`-32603`	`Registry error <status>` when the registry behind an agent, category or persona resource fails, or a missing `uri`
401	`-32001`	No key, or a wrong, revoked or expired key, or a bearer that does not start with `ozk_`

The full table is on the MCP Reference overview.