gold402-mcp

gold402_get_entry

Read-onlyIdempotent

Retrieve a specific gold-402 entry by exact or partial name, returning its URL, description, shelf, listing date, and permanent page.

Instructions

Fetch a single gold-402 entry by name (exact match preferred, falls back to partial). Returns the full record including URL, description, shelf, the date it was first listed, and the permanent listing page.

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

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.5/5.0

Behavior4/5

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

The description discloses the matching behavior (exact then partial) and lists return fields. Annotations already provide safety hints (read-only, idempotent), so the description adds meaningful behavioral detail without redundancy.

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?

The description is two concise sentences, free of fluff, and clearly structured. It communicates purpose and output without unnecessary detail.

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?

Given the low complexity (single entry fetch) and presence of an output schema, the description sufficiently covers the return content by listing all key fields (URL, description, shelf, date first listed, permanent listing page). No gaps found.

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?

Both parameters have schema descriptions, and the tool description enriches the 'name' parameter by explaining the exact/partial matching semantics. The response_format parameter is adequately described in the schema, so no additional clarification is needed.

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 clearly states the tool fetches a single gold-402 entry by name, with exact match preferred and fallback to partial. This precisely defines the action and distinguishes from search-oriented siblings.

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?

It explicitly indicates when to use: to retrieve a single entry by name. While it doesn't contrast with sibling tools like gold402_search, the scope is unambiguous enough for the agent to select appropriately.

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

Deploy Server