Skip to main content
Glama

Phrase Bank

topic_scorer_phrases
Read-onlyIdempotent

Returns the ranked phrase bank for one category: 1 to 4 word phrases a page squarely about that category would contain, ordered by similarity to the category. Use it to seed a brief. 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": {
      "taxonomy": "<taxonomy>",
      "category": "<category>"
    },
    "name": "topic_scorer_phrases"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoBank size.
categoryYesTarget category id, full path, or a unique path substring within the taxonomy (use topic_scorer_find to look one up).
taxonomyYesTaxonomy of the target category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description mostly repeats that with 'read-only and safe to retry.' It adds useful context with 'Free' and ordering by similarity, but does not add deeper behavioral detail such as rate limits or exact return structure.

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?

Two tightly written sentences front-load the return value and purpose. There is no unnecessary explanation or meandering.

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

Completeness4/5

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

For a simple three-parameter tool with complete schema coverage and no output schema, the description explains what the tool returns and how results are ordered. It could be slightly more complete about the exact return shape, but it is otherwise sufficient.

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 coverage is 100%, so all three parameters are already documented. The description adds only the notion of a single target category and phrase length, without additional parameter semantics beyond the schema baseline.

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: returns the ranked phrase bank for one category, with phrase length and ordering explained. It clearly implies this is not a scoring/gating/lookup tool, but it does not explicitly differentiate itself from the sibling tools.

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?

It gives a clear use case: 'Use it to seed a brief.' It does not state when not to use it or name sibling alternatives, though the schema's category parameter points to topic_scorer_find for lookup.

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