Function implementations
CAESAR_TOOLS with your kit’s function-tool helper. Keep the public tool names as caesar_search and caesar_read so prompts, logs, and MCP fallbacks use the same vocabulary.
MCP alternative
Use the hosted streamable-HTTP endpoint when the kit supports MCP:Authorization: Bearer $CAESAR_API_KEY when you need keyed rate limits. Omit the header for anonymous access.
Tool behavior
| Tool | Purpose | Default |
|---|---|---|
caesar_search | Find ranked documents and return doc_id handles | compact result shape |
caesar_read | Read a doc_id or URL as markdown | 12,000 character cap |
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_KEYor anonymous access.