Skip to main content
Glama

Market Brew

Query Coverage Analyzer

analyze_query_coverage

Use this when the user asks to run Query Coverage Analyzer. 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_query_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/5

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

The description adds real context beyond the annotations: it warns that the call may invoke providers, consume quota, and populate caches, which is consistent with readOnlyHint=false and openWorldHint=true. It also correctly rules out publishing and Launchpad side effects. However, it does not explain what the returned "structured analysis" contains, how long an open-world provider call may take, or what partial failures look like.

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?

It is short and front-loaded, but the opening sentence is pure boilerplate that duplicates the tool name, while the genuinely useful details (quota consumption, no publishing, generation gating) are compressed into a dense middle. One sentence is wasted and one carries too much.

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?

This is a complex, nested-parameter, open-world analysis tool with no output schema and no parameter documentation, so the description must carry more weight than it does. It never explains what "coverage" is measured against, what a "draft preview" or "comparison" looks like, or how the required crew id relates to the rest of the payload.

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

Parameters1/5

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

The schema has a single top-level body object containing roughly two dozen nested fields (crew, focus, query, topic, targetUrl, comparisonUrl, pageSize, expansionTerms, compressionLevel, generatePrompts, etc.) with 0% description coverage. The only hint in the description is "Request generation only when explicitly desired," which loosely maps to generatePrompts/recommendations and leaves everything else undocumented in both schema and prose.

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 Query Coverage Analyzer" restates the name and title rather than explaining what query coverage analysis is. "Returns structured analysis and supported comparisons or draft previews" is the only substantive content, and it is too vague to distinguish this from siblings such as analyze_query_expansion or analyze_semantic_focus.

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 trigger condition is circular (use it when the user asks for it), and no alternative tool or precondition is named. "Does not publish content or add opportunities to Launchpad" and "Request generation only when explicitly desired" are partial scoping hints, but they describe side effects rather than when to select this tool over its many 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