Skip to main content
Glama

Find Categories

topic_scorer_find
Read-onlyIdempotent

Finds categories whose path contains the query (case-insensitive substring), optionally within one taxonomy. Free. Returns up to limit hits with id and path; pass the id as category to the scoring tools.

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": {
      "query": "<query>"
    },
    "name": "topic_scorer_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for in category paths.
taxonomyNoTaxonomy of the target category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the lookup is free (no cost), matching is case-insensitive substring rather than exact, and results are capped at `limit` hits with only id and path returned.

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 short sentences, no filler: the search semantics come first, then the optional scoping, then the return shape and hand-off. Every clause carries information an agent needs.

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?

There is no output schema, and the description does cover the essential return shape (id and path, up to `limit`). It omits ordering/ranking of hits and what happens with zero results, which are minor gaps for a simple lookup tool.

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

Parameters4/5

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

Schema coverage is 67% and the description fills the main gap by explaining the practical effect of `limit` ('returns up to `limit` hits') and that `taxonomy` is optional scoping. It also documents the shape of the returned id, which matters for downstream calls. It does not spell out matching behavior for multi-word queries beyond 'contains the query'.

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+resource ('Finds categories') and pins the matching semantics (case-insensitive substring on path). It also implicitly separates itself from the scoring siblings by noting it returns ids to be passed to 'the scoring tools', so an agent can place it in the workflow without opening another 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 chain: find here, then pass the returned id as `category` to the scoring tools, and optionally narrow by taxonomy. It supplies no explicit exclusions (e.g. 'to enumerate taxonomies, use topic_scorer_taxonomies'), which keeps it below a 5.

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