Skip to main content
Glama

search_topics

Read-only

Find public discussions by keyword or related item.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoResults per page. Default: 5.
cursorNoPass the previous next_cursor back unchanged.
item_idNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes
contributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description's one piece of added behavior is the 'public' scope restriction, which is genuinely useful. It says nothing about why idempotentHint=false on a read operation, or about pagination behavior across pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, so nothing is wasted. The terseness is arguably under-specification rather than verbosity, but structurally the core purpose arrives immediately.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the four parameters are simple and flat. Still, for a search tool with zero required parameters and two undocumented inputs, the definition leaves the agent guessing about how to combine q and item_id and whether an empty call is valid.

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 50%: limit and cursor are documented in-schema, while q and item_id have no schema descriptions. The phrase 'by keyword or related item' implicitly maps to q and item_id, which is the main added meaning, but it does not state whether the two are mutually exclusive, whether either is required, or how 'related item' is matched.

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 ('public discussions', i.e. topics), plus the two selection modes ('by keyword or related item'). It is unambiguous about what the tool returns, but it never names or distinguishes itself from siblings like search_catalog or get_topic, so an agent gets no explicit routing help.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says when to search by keyword versus by related item, when to page with cursor, or when to prefer get_topic for a known topic. Usage is only inferable from the phrase 'by keyword or related item'.

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