Skip to main content
Glama

Market Brew

Query Proximity Visualizer

analyze_query_proximity

Use this when the user asks to run Query Proximity Visualizer. 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_proximity"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, and the description usefully adds context the annotations cannot convey: it may invoke providers, consume quota, and populate caches, and it explicitly does not publish content or add opportunities to Launchpad. That side-effect boundary and cost warning are exactly the kind of disclosure an agent needs before calling a non-read-only, open-world tool. It stops short of describing rate limits or latency, so it is not a 5.

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 text is short and front-loaded, and the sentence about not publishing to Launchpad is efficient. However, the opening sentence duplicates the tool name and title without adding information, and the phrase "supported comparisons or draft previews" is hedged filler rather than precise description.

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 tool with a deeply nested 30+ field schema, no output schema, and zero parameter descriptions, the definition leaves most of the invocation surface unexplained. It does well on side effects and cost, but an agent still cannot tell what inputs are required for a meaningful proximity analysis, what the analysis returns, or how to interpret results.

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 single `body` parameter contains dozens of nested, undocumented fields (crew, focus anchors/entities, comparisonUrl, compressionLevel, includeVectors, selectionStart/End, etc.). The description adds meaning for only one of them via "Request generation only when explicitly desired," which implicitly maps to generatePrompts, leaving the rest entirely unexplained. With such a rich nested schema, far more parameter guidance was needed.

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 Proximity Visualizer" merely restates the tool name and title rather than describing what query proximity analysis actually does. The only substantive claim is the vague "Returns structured analysis and supported comparisons or draft previews," which does not tell an agent what is measured (e.g., proximity between queries/anchors) or how it differs from siblings like analyze_query_coverage or analyze_query_expansion.

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 when-to-use clause is circular ("when the user asks to run [tool name]"), so it gives no real selection criteria against the many analyze_* siblings. The only concrete guidance is "Request generation only when explicitly desired," which addresses one nested flag rather than when to choose this tool over alternatives, and there are no stated exclusions or prerequisites beyond an API-key-enabled account.

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