Skip to main content
Glama

Copybook

List kinds, topics and tools

list_facets
Read-onlyIdempotent

List filter ids, plain names, technical terms and current tip counts for search_tips. Counts exclude broken and superseded tips.

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_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
langYes
kindsYes
toolsYes
topicsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered and the description needn't restate it. What it does add is a genuine data semantic: counts exclude broken and superseded tips, which changes how an agent should interpret the numbers. It doesn't mention refresh cadence or whether the facet list is exhaustive, so it stops short of 5.

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 sentences, both earning their place: the first defines the payload and its consumer, the second qualifies the counts. The most decision-relevant content is front-loaded and there is no filler.

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 zero-parameter enumeration tool with an output schema and full annotation coverage, the description supplies what the structured fields cannot: the meaning of the counts and the downstream consumer. It would be complete at 5 if it confirmed that the returned ids are directly usable as search_tips filter values.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on inputs.

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 (list) and enumerates the returned content — filter ids, plain names, technical terms, tip counts — and ties it to the search_tips tool, which distinguishes it from search_tips itself. The one weakness is that the description never uses the vocabulary of the title (kinds, topics, tools), so the agent must infer that these facets are the taxonomy of the tip corpus rather than something else.

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 'for search_tips' implies this is a discovery call made before filtering with search_tips, which is useful positioning. But it never states when to call it explicitly, gives no exclusions, and doesn't say whether the returned ids are the values accepted by search_tips filters.

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