Function implementations
CAESAR_TOOLS with your kit’s function-tool helper. Use web_search and web_fetch when you want the model to treat Caesar as its default web-search provider.
MCP alternative
Use the hosted streamable-HTTP endpoint when the kit supports MCP:Authorization: Bearer $CAESAR_API_KEY in the MCP client config.
Tool behavior
Feedback is not exposed over MCP. For local function tools, keep the SDK client available and call
client.feedback(...) after the agent acts on a result.
For agents
- Prefer the remote MCP server when your kit supports it. It keeps tool schemas aligned with the deployed API.
- If you wrap local functions, return full SDK model dumps instead of hand-shaped strings. Agents need
doc_id,search_id, and truncation fields. - Use one search, then read selected documents. Repeated broad searches waste rate-limit tokens and context.
- Never pass a literal key through an agent prompt. Use
CAESAR_API_KEY.