Skip to main content
Glama

Find a board topic

find_topic
Read-only

Fuzzy-find a knowledge-board topic path by name, e.g. to pass as search.topic.

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

Input Schema

NameRequiredDescriptionDefault
nameYestopic name or fragment, e.g. "postgres"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real context beyond them: the matching is fuzzy rather than exact, and the return value is a topic path ready to feed into another tool. It stops short of saying what happens on multiple or zero matches, which matters for a fuzzy lookup.

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 sentence with no filler; the core action leads and the downstream-use clause follows. Every element earns its place.

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 one-parameter lookup with no output schema, the description supplies what matters: fuzzy matching semantics and the shape of the result (a topic path). Only edge-case behavior (multiple matches, no match) is missing, a minor gap given the tool's simplicity.

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% and the single 'name' parameter is already documented with a fragment example, so the schema does the heavy lifting. The description only restates 'by name' and adds the consumption hint, not the input format — baseline 3 is appropriate.

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 names a specific verb ('Fuzzy-find'), a specific resource ('knowledge-board topic path'), and even the intended use of the result ('to pass as search.topic'). It does not explicitly contrast with the sibling list_topics, but 'fuzzy-find ... by name' versus a plain listing is distinguishable enough.

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

Usage Guidelines3/5

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

The phrase 'e.g. to pass as search.topic' communicates a downstream use, implying when an agent should reach for it (resolving a name before searching). However, it never states when NOT to use it or names list_topics as the alternative for enumerating topics, so guidance is implied rather than explicit.

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.