Skip to main content
Glama

Market Brew

Inspect Coordinate Geometry

analyze_orbital_drift

Use this when the user asks to run Inspect Coordinate Geometry. 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_orbital_drift"
  }
}

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?

Beyond the annotations, the description discloses that the tool requires an API-key-enabled account, may invoke providers, consumes quota, and populates caches — details the readOnlyHint=false and openWorldHint=true declarations do not supply on their own. It also bounds side effects by excluding publishing and Launchpad additions, consistent with destructiveHint=false. It stops short of describing what the structured analysis actually contains.

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 description is short and front-loads the trigger, but the first sentence is pure waste (title echo) and the closing sentence is cryptic and unattached to any identifiable parameter. The middle sentences about quota, caches, and scope exclusions are efficient and earn their place.

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 deeply nested input schema, zero parameter descriptions, and no output schema, the description needed to carry much more weight. It covers account prerequisites and side effects but says nothing about what the analysis returns, what the draft/comparison variants do, or how pagination fields behave — an agent is left guessing at invocation 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 single body parameter contains roughly thirty nested properties (crew, focus, comparisonUrl, generatePrompts, compressionLevel, etc.) with no textual meaning anywhere. The phrase "Request generation only when explicitly desired" faintly gestures at a generation flag but does not name it or explain its effect, leaving nearly all parameter semantics undocumented.

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?

The description opens with "Use this when the user asks to run Inspect Coordinate Geometry," which merely restates the title rather than naming a resource and an operation. The tool name (analyze_orbital_drift) and the title (Inspect Coordinate Geometry) describe entirely different things and neither is reconciled by the text, so an agent cannot tell what is actually being analyzed.

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 usage trigger is tautological (use it when the user asks to use it). There are useful negative scopes — "Does not publish content or add opportunities to Launchpad" — which rule out some siblings, but no positive guidance on when to choose this over the dense list of analyze_* siblings such as analyze_semantic_focus or analyze_query_expansion.

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