Skip to main content
Glama

Find topics

find_topics
Read-only

Find up to10 currently public topic names and canonical slugs. Use a slug as the topic filter of search_transcripts. Free; no key needed.

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": "find_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-open-world, and the description adds real context beyond them: results are limited to 10, only currently public topics are returned, and the call is free with no key required. It still does not describe result ordering or what happens when the query matches nothing.

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, each earning its place: what you get, what to do with it, and the cost/auth profile. The information is front-loaded with the result shape before the follow-up action.

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 and helpful annotations, the description covers scope, result cap, cost, and next-step usage. The main omission is the semantics of the required query input, which is the one thing an agent cannot infer from the unlabeled schema.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is required with length constraints (2-100 chars), so the description must carry the meaning of 'query'. It never mentions the query argument at all — no hint about whether it is a prefix, substring, or fuzzy match, or how matching affects the returned topic list.

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?

States a specific verb (find) and resource (topic names and canonical slugs), plus useful scope modifiers: 'currently public' and 'up to 10'. It does not explicitly distinguish itself from the sibling get_topics, so an agent may still hesitate between the two, keeping it below a 5.

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 concrete downstream guidance — take a returned slug and use it as the topic filter of search_transcripts — which is exactly the kind of chaining instruction an agent needs. There is no exclusion guidance (e.g. when to prefer get_topics), so it stops short of full when/when-not coverage.

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