Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

TF-IDF term gap vs competitor pages

seo-content_tfidf-term-gap
Read-onlyIdempotent

Find stemmed terms common among competitor pages but missing or under-used in a draft, ranked by TF-IDF gap. Price $0.04 USDC. POST /api/v1/seo-content/tfidf-term-gap. An unpaid call returns the x402 payment terms and does not run.

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": {
      "draft": "<draft>",
      "competitors": "<competitors>"
    },
    "name": "seo-content_tfidf-term-gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesdraft, string, length 1 to 200000. Required.
limitNolimit, integer, from 1 to 200. Required.
languageNolanguage, string. Required.en
competitorsYescompetitors, array. Required.
minDocFrequencyNominDocFrequency, integer, from 1 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
gapsNogaps. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
lowConfidenceNolowConfidence. Boolean.
duplicatesIgnoredNoduplicatesIgnored. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), but the description adds details the annotations cannot: pricing at $0.04 USDC, the POST endpoint, and the key behavior that an unpaid call returns x402 payment terms instead of running. That is meaningful operational context. It does not describe result shape, though an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences that lead with the core purpose, followed by pricing, endpoint, and the payment-gate caveat. Nothing is wasted, though the endpoint and price metadata occupy space that could have carried input-format guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and rich annotations reduce what the description must cover, and cost and payment behavior are handled well. However, for a tool that takes up to 200,000 characters of draft text plus a competitors array that accepts either strings or HTML objects, the definition never says which input form is expected, which is a real gap for correct invocation.

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

Parameters3/5

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

Schema description coverage is reported at 100%, so the schema itself carries the parameter burden and baseline 3 applies. The description adds no meaning about how draft or competitor entries should be supplied (raw text vs. HTML) or what limit and minDocFrequency do. The semantic descriptions in the schema are themselves thin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource: 'Find stemmed terms common among competitor pages but missing or under-used in a draft, ranked by TF-IDF gap.' That wording is specific enough to tell it apart from siblings such as topic-coverage-score or near-duplicate-detect. It stops short of naming an alternative explicitly, so it falls just below the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use is only implied: the phrase 'missing or under-used in a draft' hints at auditing a draft before or after writing. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling tool, so an agent has to infer the workflow fit.

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