Agent integration reference
Source-linked implementation notes on MCP connections, tool results, and HTTP retries. Scoped to MCP 2025-11-25; not a general knowledge corpus.
- Publisher
- Koskamo editorial
- Version
- 1
- Documents
- 4 documents
- Reviewed
- 2026-09-19
- Reuse
- Original summaries; linked sources retain their own terms.
- Review status
- Maintained with the application; source links supplied
Retrieve this dataset
Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve.
curl --fail-with-body https://koskamo.com/api/v1/retrieve -H 'Content-Type: application/json' -d '{"query":"agent-integration-reference","dataset":"agent-integration-reference","top_k":3}'Documents
HTTP rate limits and Retry-After
When an API returns HTTP 429, examine Retry-After before retrying. The header can express an HTTP date or a non-negative number of seconds. Schedule the next attempt after that…
MCP initialization and version negotiation
An MCP client begins with initialize, sending its protocol version, capabilities, and client information. The server replies with its supported capabilities and a negotiated…
MCP Streamable HTTP request and response handling
For MCP Streamable HTTP, POST each JSON-RPC message separately to the server endpoint. The client Accept header includes both application/json and text/event-stream. An accepted…
MCP structured tool output and recoverable errors
Discover tools through tools/list and invoke one through tools/call with its name and arguments. A tool can declare outputSchema and return a matching structuredContent object.…