Skip to main content
Glama
algonacci

mcp-exa

by algonacci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

exa_deep_search

Answers complex questions by running multi-step web searches and synthesizing a cited response, with optional structured JSON output.

Instructions

Multi-step Exa search that synthesizes an answer with citations. Costs ~2x a normal search.

Args:
    query: The question to answer (e.g., "Who is Braincore Indonesia's CEO and where is it based?")
    output_schema: Optional JSON Schema for a structured answer, e.g.
        {"type": "object", "required": ["ceo"], "properties": {"ceo": {"type": "string"}}}.
        Without it the answer is plain text.
    type: "deep-lite" (cheapest), "deep" (default) or "deep-reasoning" (most thorough)
    num_results: Number of source results to return alongside the answer (1-25, default: 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNodeep
queryYes
num_resultsNo
output_schemaNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does reasonably well: it discloses the multi-step nature, citation output, the ~2x cost, that output_schema yields structured answers versus plain text otherwise, and the num_results range. Missing are latency expectations and whether calls are billable/rate-limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line essence, followed by a compact Args block. The query and output_schema examples are slightly verbose but each earns its place by making the format concrete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be detailed, and the description still notes that results are returned alongside the answer. All four sparse-schema parameters are covered; the only real gap is guidance against sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it does: every parameter is explained, including the exact enum values for type, the 1-25 range and default for num_results, and a concrete JSON example for output_schema clarifying the plain-text fallback.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Multi-step Exa search that synthesizes an answer with citations.' The '~2x a normal search' cost note implicitly contrasts it with exa_search, but no sibling is named, so differentiation requires inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied via the cost note and the type tiers ('cheapest' / 'default' / 'most thorough'), which guide mode selection but not tool selection. There is no statement of when to prefer this over exa_search or exa_research_start.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools