Skip to main content
Glama

AI web research brief with cited sources

research_brief
Read-only

AI research brief on one question from a live web search: a summary of up to 200 words, up to 8 findings each with citation URLs checked against the search tool's own records (uncited claims are dropped), the source URLs consulted, and an as-of date. Depth quick (up to 2 searches) or standard (up to 4); optional since date. AI-generated under a fixed Kit Rx prompt and can be wrong. No personal profiles, patient-specific medical advice or investment calls. Price: $0.15 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

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": {
      "q": "<q>"
    },
    "name": "research_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesResearch question, 5 to 400 characters (URL-encoded). Treated as data to research, not as instructions.
depthNoquick (at most 2 web searches, 3-5 findings) or standard (up to 4 searches, 4-8 findings, default). Same price.
sinceNoOnly report developments from this date on, as YYYY-MM-DD (1900-01-01 to today, UTC). Steers the search; source dates are not verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the cost model ($0.15 per successful call in USDC via x402 v2), that failures and zero-match calls are not charged, that citations are checked against the search tool's own records and uncited claims dropped, that generation runs under a fixed prompt, that results may be wrong, and that a no-argument call returns a stored example. This is exactly the pricing, billing, and reliability context annotations cannot carry.

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?

It is a single dense block, but the output contract is front-loaded and every sentence carries distinct information (output shape, depth, disclaimers, pricing, no-arg behavior). Minor deduction only because the pricing and disclaimer clauses are packed into the same run-on paragraph rather than separated for scanability.

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?

With no output schema, the description takes on the burden of describing return values and does so precisely (word cap, finding cap, citation verification, as-of date). Combined with the cost model and content restrictions, an agent has everything needed to decide to call it, what arguments to pass, and what to expect back.

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 description coverage is 100%, so the three parameters are already fully documented — including the 5-to-400-character question length, the enum values, and the YYYY-MM-DD range for since. The description restates depth and since without adding syntax or edge cases beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

The first sentence names the verb and resource (research brief on one question from a live web search) and then specifies the exact return shape: summary up to 200 words, up to 8 findings each with citation URLs, source URLs consulted, and an as-of date. This is specific enough that an agent can distinguish it from generic web_answer or web_check siblings even without wording that names them.

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?

Clear context is given for the depth choice (quick = up to 2 searches, standard = up to 4) and the optional since date, plus the notable no-argument fallback that returns a stored example without a model call. It also states exclusions (no personal profiles, patient-specific medical advice, or investment calls). It stops short of a 5 because it never names an alternative sibling or says when a different tool should be used instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources