Skip to main content
Glama

Market Brew

HTML TF-IDF Analyzer

analyze_html_tf_idf

Use this when the user asks to run HTML 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_html_tf_idf"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/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 mutation/external-call profile is partly structured. The description does add real value beyond that: provider invocation, quota consumption, cache population, and the explicit negative scope (no publishing, no Launchpad adds). However, it says nothing about cost magnitude, latency, or whether repeated calls with the same body are safe given non-idempotency.

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, with no filler beyond the necessary. But the leading sentence is pure waste since it duplicates the name, and the mixed bag of caveats (quota, caches, Launchpad, request generation) is presented without structure or priority.

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 input schema, no output schema, and zero schema descriptions, the definition leaves an agent unable to construct a valid, meaningful call. It never explains what TF-IDF analysis on HTML produces, what "supported comparisons" or "draft previews" mean, or which nested fields are mutually exclusive.

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?

Schema description coverage is 0% and the body object nests roughly two dozen properties (targetUrl, query, focus.anchors, focus.entities, content, prompts, comparisonUrl, expansionTerms, pageSize, etc.), none of which the description mentions. With such a large undocumented nested schema, the description carries the full burden and adds no parameter meaning at all.

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 line, "Use this when the user asks to run HTML TF-IDF Analyzer," merely restates the tool name and title rather than describing what the analysis does or what it measures. The only added content ("Returns structured analysis and supported comparisons or draft previews") is too generic to distinguish it from siblings such as analyze_html_bm25 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: use the tool when the user asks for the tool. There is no stated when-not, no prerequisite, and no routing to any of the many sibling analyzers. The single boundary note ("Does not publish content or add opportunities to Launchpad") is a scope exclusion, not usage guidance.

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