Skip to main content
Glama

Gate Text

topic_scorer_gate
Read-onlyIdempotent

Pass/fail check: does the text rank within the top min_rank categories of its target taxonomy? Returns pass, the target's rank and gap to #1, the taxonomy's top five, and the unused phrases to work in. Use it as a content-pipeline gate. Free; read-only and safe to retry.

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>",
      "taxonomy": "<taxonomy>",
      "category": "<category>"
    },
    "name": "topic_scorer_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoScore the whole text as the mean of 8,192-char chunks instead of only the first 8,192 chars.
textYesThe page or draft text to score, as plain text or HTML (tags are stripped). 1 to 32768 characters. URLs are not fetched; send the content.
phrasesNoPhrase bank size for the target category (0 skips it).
categoryYesTarget category id, full path, or a unique path substring within the taxonomy (use topic_scorer_find to look one up).
min_rankNoHighest passing rank.
taxonomyYesTaxonomy of the target category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'read-only and safe to retry' is largely redundant. However, the description earns credit by disclosing the return payload (pass, rank, gap to #1, top five, unused phrases) in the absence of an output schema. It does not specify failure conditions or error behavior beyond 'pass'.

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?

Three compact sentences, front-loaded with the pass/fail decision and followed by returns and safety. Every clause carries information; nothing is padding.

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

Completeness5/5

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

With no output schema, the description takes on the burden of explaining returns and does so concretely (pass, rank, gap to #1, top five, unused phrases). Combined with full schema coverage and annotations covering safety, an agent has everything needed to call it correctly.

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 every parameter including `full`, `phrases`, `min_rank`, `category` and `taxonomy` is already documented in the schema. The description references `min_rank` and 'target taxonomy' but adds no syntax or interpretation beyond what the schema states; 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?

States a specific verb and resource: a pass/fail check of whether the text ranks within the top `min_rank` categories of its target taxonomy. The phrase 'content-pipeline gate' pins down the role and implicitly separates it from the raw-scoring sibling topic_scorer_score, so an agent can select it without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear usage context ('use it as a content-pipeline gate') and points to topic_scorer_find for category lookup, which is a genuine routing hint. It stops short of explicitly saying when to prefer topic_scorer_score over this gate, so it lacks full when/when-not contrast.

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