Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

keyword_ngrams_extractor

Extract top keyword unigrams, bigrams and trigrams with density

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": "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 observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Extract' signals a non-mutating analysis operation and 'with density' hints at an additional output metric, but it does not state whether this is read-only, how density is computed, or what the return shape looks like. This is minimally adequate but leaves gaps.

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

Conciseness5/5

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

A single front-loaded sentence with no wasted wording. It communicates the operation and the three n-gram sizes efficiently.

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?

The schema is fully described and the tool is simple, but with no output schema the description does not explain what 'density' returns or what the result structure looks like. For a text-analysis extractor this is mostly complete, but the output contract remains implicit.

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?

The schema has 100% description coverage for all four parameters. The description only restates the n-gram sizes and density concept, adding no meaning beyond what the schema already documents, so baseline 3 applies.

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

Purpose5/5

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

The description states a specific action and resource: extract keyword unigrams, bigrams and trigrams with density. It is unambiguous and sufficient to distinguish it from the unrelated SEO diagnostics in the sibling list.

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?

No when-to-use or when-not-to-use guidance is provided. There are no direct n-gram siblings, so an agent could reasonably infer it is the keyword extraction option, but the description itself gives no usage context or exclusions.

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