Skip to main content
Glama

Market Brew

Search Citation Explorer

analyze_search_citation

Use this when the user asks to run Search Citation Explorer. Returns structured analysis and supported comparisons or draft previews for an API-key-enabled account. May invoke providers, consume quota and populate caches. Does not publish content or add opportunities to Launchpad. Request generation only when explicitly desired.

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": {
      "body": "<body>"
    },
    "name": "analyze_search_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior3/5

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

The description goes beyond the annotations by disclosing real side effects: provider invocation, quota consumption, and cache population, plus a clear negative boundary (no publishing, no Launchpad additions). However, it omits the account prerequisite details (what "API-key-enabled" requires), whether calls are safe to retry given idempotentHint=false, and roughly how much quota a call can consume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The four sentences are short and the side-effect and boundary statements are front-loaded, which is good. But the opening sentence is wasted space that duplicates the title, and the mixed bundle of analysis, comparison, and draft-preview outputs in one sentence is loose rather than structured.

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

Completeness2/5

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

With a deep nested schema, 0% parameter documentation, no output schema, and no sibling differentiation, the description is far too thin for the tool's complexity. It covers side effects and non-goals adequately but leaves the agent without enough to build a valid body payload or anticipate the response shape.

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% and the body object nests roughly two dozen undocumented properties (focus.anchors, entities, snapshotId, rankingSensorId, compressionLevel, etc.). The description explains none of them, offering only the implicit mapping of "Request generation only when explicitly desired" to generatePrompts, leaving the parameter space essentially unexplained.

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

Purpose2/5

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

"Use this when the user asks to run Search Citation Explorer" restates the tool's own name and title rather than describing the operation, which is close to tautology. The second sentence ("Returns structured analysis and supported comparisons or draft previews") adds a partial hint about output, but the agent still cannot tell what a "search citation" analysis actually computes or how it differs from the many analyze_* siblings.

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

Usage Guidelines2/5

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

The only selection guidance is circular — invoke it when the user asks for it — with no conditions, prerequisites, or named alternatives among the analyze_* family. "Request generation only when explicitly desired" is a genuine conditional, but it governs an option rather than telling the agent when to choose this tool over siblings.

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