Skip to main content
Glama
Sign In
fetchira

fetchira

by ImmuneFOMO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

deep_research

Gather multi-source research across web, news, and academic providers, then generate a plan, run a session, and fetch the final report.

Instructions

Deep research over multiple sources (parallel, exa, tavily, tinyfish, linkup, you, gemini_web, grok_web, chatgpt_web); may take minutes. gemini_web and chatgpt_web first return a research PLAN plus a session: pass that session with query "start" to run it, or with a revised request to replace the plan. gemini returns the finished report in the same call; chatgpt runs ~5-30 min after "start" — call again with the returned session to fetch the report (model is ignored there). Knobs: topic, recency, domains, depth ("deep" is slower/pricier). Provider-specific extras → call usage(provider=…).

Input Schema

NameRequiredDescriptionDefault
fileNoAbsolute paths of local files/images to attach and ask about. Local stdio only; hosted HTTP rejects file inputs because it cannot access the caller's filesystem. Web providers only; defaults to grok_web when no `provider` is forced.
modeNoProvider-specific mode. grok: "auto"/"fast"/"expert"/"heavy" (search defaults to fast, deep_research to heavy then expert); keenable "realtime"/"pro"; nimble "standard".
depthNoDepth: "standard" (default) or "deep" — deep is slower and may spend a paid balance (exa deep-reasoning, parallel core processor, linkup/you deep effort, grok heavy).
modelNoWeb-provider model and/or thinking level. Call usage with that provider for available names and levels; omit to use its default. Ignored by the API providers.
queryNoThe search query (or a follow-up message when `session` is set). Optional only when polling a running deep-research `session` for its report.
topicNoResearch niche: "web" (default), "news", or "academic" — steers to a fitting backend.
domainsNoRestrict to these domains; prefix one with "-" to exclude it (e.g. ["nature.com","-reddit.com"]).
recencyNoRecency filter: "day"/"week"/"month"/"year" or an ISO date (e.g. "2024-01-01").
sessionNoResume token from a previous web-provider result; continues that conversation on the same provider. Web providers only.
providerNoForce a specific provider instead of the priority order.
max_resultsNoMaximum number of results (default 5, capped at 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses the long runtime, the async polling pattern for chatgpt_web, the session lifecycle, and that model is ignored during chatgpt report polling. It adds substantial operational context beyond the schema.

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?

The description front-loads purpose and timing, then explains session flow, then lists knobs. It is dense but every sentence carries operational detail; it could be more scannable with bullets, but it remains readable and appropriately sized for a complex tool.

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

Completeness5/5

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

For an 11-parameter tool with no annotations and no output schema, the description covers the critical multi-step session lifecycle, timing expectations, provider-specific behavior, and key knobs. It leaves return-format minutiae to runtime behavior but explains the essential async patterns an agent must know.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning about the session/query relationship, the cost and speed tradeoff of depth='deep', and how provider-specific extras are discovered via usage. It goes beyond the structured parameter definitions.

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?

The description states a specific verb and resource: 'Deep research over multiple sources' and lists the providers it can use. It implicitly distinguishes from siblings like search through 'deep research' and 'may take minutes', but does not explicitly name an alternative.

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

Usage Guidelines4/5

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

It explains the session workflow for gemini_web and chatgpt_web (pass the session with query 'start' or a revised request) and that chatgpt requires a follow-up call 5-30 minutes later. It does not explicitly say when to choose this over search or browser, or when not to use it, but the context is clear.

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