Skip to main content
Glama

Market Brew

Query Expansion Explorer

analyze_query_expansion

Use this when the user asks to run Query Expansion 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_query_expansion"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior3/5

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

With readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false already supplied, the description still adds real value: it warns that the call may invoke providers, consume quota and populate caches, and scopes blast radius by saying it does not publish content or add opportunities to Launchpad. That is genuine beyond-annotation context, though side effects like latency, queuing or per-account rate limits go unmentioned.

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?

Four short sentences, front-loaded with the trigger and followed by effects and exclusions, with essentially no filler. Length is appropriate; the opening line simply spends words restating the name.

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?

For a quota-consuming, provider-invoking tool with a deep nested body, no output schema and zero parameter descriptions, the definition leaves too much to inference. An agent knows the call is not read-only and is not destructive, but not what to put in `body` or what shape the analysis returns.

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?

A single required `body` object carries roughly twenty nested properties (query, focus, expansionTerms, recommendations, compressionLevel, includeVectors, website, etc.) at 0% schema description coverage, and the description names none of them. The only semantic nudge is the generation caveat that loosely maps to generatePrompts; the rest of the parameter surface is undocumented anywhere.

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 Expansion Explorer" restates the title rather than defining the operation; the only substantive claim is "Returns structured analysis and supported comparisons or draft previews." Nothing explains what query expansion means here or how it differs from the many sibling analyze_query_* tools.

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?

No explicit when-to-use or when-not relative to close siblings like analyze_query_coverage or analyze_query_proximity. The single actionable clause, "Request generation only when explicitly desired," hints at gating the generatePrompts path but is not framed as a selection rule.

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