Skip to main content
Glama

Market Brew

META Title Vector Similarity Analyzer

analyze_meta_title_vector_similarity

Use this when the user asks to run META Title 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_meta_title_vector_similarity"
  }
}

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, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description still earns credit by adding cost and side-effect context the annotations cannot express: it may invoke external providers, consume quota and populate caches, and it explicitly scopes out publishing and Launchpad additions. The only gap is the trigger phrase that is really usage guidance, not behavior.

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?

Four short sentences with no padding, but the opening sentence is pure waste since it repeats the title. The most useful content — quota consumption and the non-publishing scope — sits in the middle rather than being front-loaded.

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 request body, no output schema and 0% parameter documentation, the description covers the behavioral side reasonably but leaves the entire input contract unexplained. An agent could not construct a valid body from this definition alone.

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 required parameter is a deeply nested body with dozens of sub-properties (crew, focus, draft, comparisonContent, generatePrompts, compressionLevel, includeVectors, etc.). The description never explains any of them; only 'request generation' faintly gestures at generatePrompts and 'supported comparisons or draft previews' at the comparison/draft fields. With a complex nested schema and zero coverage, the description should have compensated and does not.

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 META Title Vector Similarity Analyzer" restates the name and title rather than describing the operation, which is close to tautology. The second sentence adds only a vague sense of output ("structured analysis and supported comparisons or draft previews") and never distinguishes it from close siblings such as analyze_heading_vector_similarity or analyze_meta_title_tf_idf.

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 ('when the user asks to run' the tool), so it gives no real signal about when this analyzer applies versus its siblings. It does contribute two genuine constraints — 'Request generation only when explicitly desired' and 'Does not publish content or add opportunities to Launchpad' — but there is no positive when-to-use guidance or named alternative.

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