Skip to main content
Glama

get_web_research_synthesis

Read-only

Governed web research synthesis with cryptographic receipt. Agent submits a research question; returns an AI synthesis across live web sources with every source domain bound into an ML-DSA-65 signed receipt anchored on Base. $1.00 USDC per 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": {
      "question": "<question>"
    },
    "name": "get_web_research_synthesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: a per-call price of $1.00 USDC, that sources are live web, and that output includes an ML-DSA-65 signed receipt anchored on a blockchain. It stops short of explaining failure/charge semantics (e.g., whether billing occurs on error) or 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?

Three tight sentences, front-loaded with what the tool produces and what makes it distinctive, ending with the price. No filler or marketing padding, though 'governed' is an undefined qualifier that spends a word without adding precision.

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 one-parameter, no-output-schema tool this covers most of what an agent needs: purpose, source type, output composition (synthesis plus verifiable receipt), and cost. The missing piece is routing relative to the many sibling syntheses, which matters given how many near-identical names exist in the catalog.

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?

There is one parameter with 0% schema description coverage, so the description must carry the meaning, and it does partially by clarifying that 'question' is a natural-language research question rather than a keyword query. It adds nothing about acceptable scope, phrasing, or what the 5-500 character bound implies for a good prompt, leaving the gap only partially closed.

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 concrete verb+resource ('Agent submits a research question; returns an AI synthesis across live web sources') and names the distinctive artifact (signed receipt anchored on Base). It is clearly separable from the domain-scoped siblings (case law, company intelligence, competitive landscape) by virtue of being the general web-research variant, but it never states that routing rule explicitly.

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: an agent can infer it is for open-ended web research questions rather than the domain-specific syntheses. There is no explicit when-to-use, when-not-to-use, or 'prefer X synthesis for legal/financial questions' guidance, and no prerequisites are stated. The $1.00 per call note does give a useful cost signal for deciding whether to invoke.

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