Skip to main content
Glama

Market Brew

META Description TF-IDF Analyzer

analyze_meta_description_tf_idf

Use this when the user asks to run META Description TF-IDF 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_description_tf_idf"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/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 call may invoke external providers, consume quota, and populate caches, and that it requires an API-key-enabled account. It also bounds the blast radius by stating it does not publish content or add opportunities to Launchpad, which usefully supplements destructiveHint=false with concrete scope.

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 definition is short and front-loads the usage clause, but the opening sentence is pure filler that repeats the title. The remaining sentences carry real information about quota, auth, and scope, so the text is lean but not optimally structured.

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, entirely undocumented input object and no output schema, the description says nothing about how to populate body, which fields are mutually exclusive, or what the analysis returns. It covers the safety and quota profile adequately but leaves the parameter contract, the main source of call errors, unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0% and the body object nests dozens of properties (crew, focus.anchors, focus.entities, content fields, comparisonUrl, compressionLevel, generatePrompts, etc.). The description mentions none of these, so an agent gets no meaning for query, topic, useTopCluster, includeVectors, or the generation flags beyond guessing from property names.

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 first sentence merely restates the tool title ('Use this when the user asks to run META Description TF-IDF Analyzer'), which is tautological rather than explanatory. Only the phrase about returning 'structured analysis and supported comparisons or draft previews' hints at output, and nothing distinguishes it from siblings like analyze_meta_title_tf_idf or analyze_html_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 when-to-use clause is circular (use it when the user asks for it) and gives no criteria for choosing this over the many sibling analyzers. The single genuine guideline, 'Request generation only when explicitly desired,' is a narrow conditional rather than routing guidance, and no when-not conditions or prerequisites for the API-key account are stated.

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