Skip to main content
Glama

list_help_topics

List the Ski Club help (FAQ) topics: slug, name, intro, number of FAQs and the topic's help page url. Pass a slug to get_help_topic.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It discloses the shape of the returned data (a useful substitute for a missing output schema) but never states that this is a read-only operation, whether results are paginated or complete, or whether any auth is required.

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 short sentences with zero filler. The resource and returned fields are front-loaded, and the sibling routing note follows immediately after.

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?

Without an output schema, the description compensates well by naming exactly what each topic record contains. Missing only secondary details such as whether the list is paginated or how failures surface, which for a simple no-argument listing tool are minor.

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?

The tool takes zero parameters and the schema is empty, so there is no parameter semantics to explain. The description implicitly confirms this by pointing slug-taking to a different tool, which is the most useful thing it could say here.

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 ('List') and a specific resource ('Ski Club help (FAQ) topics'), then enumerates the fields returned: slug, name, intro, FAQ count, and help page url. It also routes the agent to the sibling get_help_topic, so the boundary between listing and fetching is unambiguous.

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?

The sentence 'Pass a slug to get_help_topic' tells the agent when to escalate from this listing to the detail tool. It gives a clear routing condition but does not explicitly state the inverse case (use this tool first to discover available slugs), leaving that to inference.

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