Skip to main content
Glama

research_any

Search multiple sources with a fallback chain, automatically trying the next API or public browser search page when one is unavailable. Runs read-only without accounts or session clicks.

Instructions

Search several sources with a fallback chain: if one API is closed, try the next best one, including the public search page in the browser.

Read-only: no account is used, nothing is posted, nothing is clicked in your session. (If you want your own logged-in session searched, connect the extension bridge - that is your one-click choice, never done silently.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "research_any"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
sourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does more than most: it states read-only status, that no account is used, that nothing is posted or clicked in the session, and that it will silently fall back to other APIs or the public browser search page. The opt-in bridge note also makes the consent model explicit, which is valuable for an agent deciding whether the call could touch a user session. It stops short of saying what happens when every source in the chain fails, or whether fallbacks mean slower or non-deterministic latency.

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 purpose and fallback behavior are front-loaded in the first sentence, and the read-only guarantee follows immediately; little is wasted. The parenthetical about the extension bridge is slightly long but it earns its place by resolving a real ambiguity about session access.

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

Completeness3/5

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

With three parameters, no annotations, and no output schema, the definition needs to do real work; it covers the safety and fallback story well but leaves the parameter surface and the shape of results unexplained. An agent could call it, but could not predict how to constrain sources or how many results come back.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not. 'Several sources' hints at the sources parameter but never states its format or permitted values, and the limit parameter with its default of 8 and the query semantics get no mention at all.

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 gives a specific verb and scope: 'Search several sources with a fallback chain'. That is more informative than a bare name restatement, but it never says which sources are searched or how it differs from siblings like research_source or research_collect.

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?

The description implies 'use this when you want a query tried across multiple sources', and it offers one alternative path (connect the extension bridge for a logged-in session search). It gives no explicit when-not guidance and never names a sibling tool as an alternative, so routing between research_any and research_source is still left to inference.

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