Skip to main content
Glama

askround_research

Ask one research question across multiple AI assistants with web search and merge their claims, support counts, passages, and cited sources, prioritizing primary sources.

Instructions

Ask a research question to every assistant with web search and merge the answers: the claims they make, how many providers support each, each provider's passage, and the sources they cited with primary ones (repositories, licence texts, papers, official docs) first. Support is agreement among assistants, not proof.

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": {
      "question": "<question>"
    },
    "name": "askround_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsNodefault 1
max_costNorefuse, before any call, a run estimated above this (USD)
questionYes
providersNoonly these providers (default: every one with a key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: it fans out to every provider, merges claims, counts supporting providers, and ranks primary sources first, plus a caveat that agreement is not proof. It omits cost/latency implications of multi-provider fan-out and whether the call is read-only, which matters for a tool that spends money across providers.

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?

A single dense sentence, front-loaded with the core action and followed by the output contract and a caveat. Every clause carries information; the only cost is that the length makes it slightly harder to scan than a two-sentence split would be.

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?

For a 4-parameter tool with no output schema and no annotations, the description covers the essential return content (claims, support counts, per-provider passages, ranked sources) and the interpretation caveat. What is missing is operational context — expected cost, latency, or failure behavior when a provider is unavailable.

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

Parameters3/5

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

Schema coverage is 75%, so the schema already documents most parameters (runs, max_cost, providers, question). The description adds no meaning beyond that — it never mentions cost capping, provider selection, or repeated runs, so it neither compensates for the remaining gap nor enriches the documented ones.

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 opens with a specific verb and resource ('Ask a research question to every assistant with web search and merge the answers') and even sketches the merged output shape. It does not, however, distinguish itself from siblings like askround_ask or askround_answer, so an agent must infer the difference from names alone.

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: the tool suits questions where cross-provider agreement matters, and the closing caveat ('Support is agreement among assistants, not proof') hints at when to trust the result. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools.

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