gold402-mcp

gold402_list_sections

Read-onlyIdempotent

List the shelves (categories) of the gold-402 directory with entry counts. Use the returned section IDs to filter searches in gold402_search.

Instructions

List the shelves (categories) of the gold-402 directory with an entry count for each. Use the returned section id as the 'section' filter in gold402_search.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive behavior, and the description adds beyond that by saying the tool returns counts and section IDs and how those IDs feed into search. This is useful behavioral/return context without contradicting the annotations.

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, purposeful sentences: the first names the action and result, the second gives the concrete integration hint. No filler, repetition, or wasted words.

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

Completeness5/5

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

For a simple list tool with safe annotations, a one-parameter schema, and an output schema, this description is complete: it explains what the tool lists, what it returns, and how to use the result in a sibling tool. No missing contextual element is apparent.

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?

The description is silent on the response_format parameter, but the schema itself documents that parameter thoroughly with an enum, default, and usage note. The description adds no parameter-level meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

The description uses a concrete verb and resource ('List the shelves (categories) of the gold-402 directory') and adds a useful output detail ('entry count for each'), clearly distinguishing it from the sibling search/retrieval/endpoint tools.

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 description tells the agent the primary downstream use ('Use the returned section id as the 'section' filter in gold402_search'), which gives clear context for when to call it. It does not explicitly say when not to use it versus alternatives, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server