Skip to main content
Glama

Market Brew

BM25 Content Analyzer

analyze_html_bm25

Use this when the user asks to run BM25 Content 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_bm25"
  }
}

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?

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description genuinely adds value beyond that: it warns that providers may be invoked, quota consumed and caches populated, and it draws an explicit boundary (no publishing, no Launchpad opportunities). It stops short of explaining why the call is non-idempotent or what an API-key-disabled account experiences.

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 filler prose, and the quota/cache warning arrives early enough to matter. However, the opening sentence is pure tautology and consumes the highest-attention position that should have carried the actual purpose.

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?

This is a high-complexity tool: one deeply nested request body, no output schema, and heavy cost side effects. The description covers cost and safety but leaves the entire request shape and the nature of the returned analysis unspecified, so an agent cannot construct a correct call from the definition alone.

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% across a single top-level `body` object with roughly thirty nested properties (query, topic, content, focus, expansionTerms, includeVectors, compressionLevel, pageSize, rankingSensorId and more). The description mentions none of them and only indirectly alludes to `generatePrompts` via "request generation". An agent gets no help mapping intent to fields.

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 BM25 Content Analyzer" restates the title rather than explaining what BM25 analysis of HTML content produces. The second sentence gestures at "structured analysis and supported comparisons or draft previews" but never says what is being analyzed (an HTML page's content against a query/topic) or how it differs from the sibling 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 only when-to-use rule is circular (use it when the user asks for it). No alternatives are named even though analyze_html_tf_idf, analyze_query_coverage, and analyze_semantic_focus occupy adjacent territory. "Request generation only when explicitly desired" is a genuine constraint, but it covers one flag rather than the tool's usage envelope.

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