Skip to main content
Glama

Market Brew

Heading Vector Similarity Analyzer

analyze_heading_vector_similarity

Use this when the user asks to run Heading Vector Similarity 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_heading_vector_similarity"
  }
}

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 adds real value beyond the annotations by disclosing that the call may invoke providers, consume quota, and populate caches, and that it does not publish content or add to Launchpad (consistent with destructiveHint=false). However, it never says what the analysis is computed against or what the structured output contains, leaving the core behavior opaque.

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?

At four short sentences it is not bloated, and the usage statement is front-loaded. But the first sentence is pure tautology and the second is generic filler, so several clauses fail to 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?

For a tool with a large nested input schema, no output schema, and no parameter documentation, the description leaves the agent without the information needed to build a correct request. It covers cost/side-effect warnings but not what the tool computes, what inputs matter, or what comes back.

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% on a deeply nested body object with dozens of properties (content, comparisonUrl, includeVectors, compressionLevel, focus, generatePrompts, pageSize), and the description explains none of them. The only hint is "Request generation only when explicitly desired," which loosely gestures at the generatePrompts flag but adds no semantics.

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 opening sentence, "Use this when the user asks to run Heading Vector Similarity Analyzer," simply restates the tool name and title. The remainder ("Returns structured analysis and supported comparisons or draft previews") is generic and never explains what heading vector similarity actually measures or how it differs from the sibling analyze_meta_title_vector_similarity.

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?

"Use this when the user asks to run [tool name]" is a tautological trigger that gives no real routing signal against the many analyze_* siblings. There is a partial negative scope ("Does not publish content or add opportunities to Launchpad") and one conditional ("Request generation only when explicitly desired"), but no positive when-to-use criteria or named alternatives.

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