Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_keyword_ngrams_extractor

Extract top unigrams, bigrams, and trigrams from text with density scores to identify keyword patterns for SEO and content optimization.

Instructions

[SEO & GEO Readiness] Extract top keyword unigrams, bigrams and trigrams with density Measured p50 13 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://seo.caelaralabs.com.

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": {
      "text": "<text>"
    },
    "name": "caelara_seo_keyword_ngrams_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoResults per n-gram size (default 15)
textYesText to analyze
max_nNoLargest n-gram size 1-3 (default 3)
include_stopwordsNoKeep stopword-edged phrases

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does add two useful facts — measured latency (p50 13 ms, p95 15 ms) and that the call goes to a remote endpoint (https://seo.caelaralabs.com) — but it omits whether this is read-only, what the response shape is, and any failure or auth behavior.

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?

Two short sentences with the purpose front-loaded and no padding. However, the benchmark citation interrupts the sentence flow, and the phrase '...trigrams with density Measured p50 13 ms' reads as a run-on, slightly hurting parseability.

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?

The tool has no output schema and no annotations, so the description is the only place to learn what comes back — yet it never describes the return structure (e.g. ranked n-grams with counts and density scores) or how the four parameters interact. For a standalone extractor with an undocumented response, this leaves a real gap.

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 100%, so all four parameters (top, text, max_n, include_stopwords) are already documented in the schema. The description adds only the loose notion of n-gram sizes and density; baseline 3 applies when the schema does the work.

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?

The description states a specific verb and resource: 'Extract top keyword unigrams, bigrams and trigrams with density.' That is concrete and distinguishable from the surrounding SEO validators/auditors, though it never explicitly contrasts itself with a sibling, and the trailing 'with density' is left grammatically dangling.

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?

There is no when-to-use guidance, no prerequisites, and no exclusions or named alternatives. The only hint of usage is the '[SEO & GEO Readiness]' tag, which implies a context but does not tell an agent when this extractor is the right choice over, say, the compositing or auditing tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools