TheDiscList Public MCP

search_discs

Search and filter disc golf discs by text query, brand, category, speed/glide range, stability score range, flight tag, and canonical flight class. Returns up to 50 bounded results with stable IDs and canonical URLs.

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

Input Schema

Name	Required	Description
`tag`	No	Filter by flight tag (e.g. 'Lockdown Fade', 'True Flight', 'Progressive Turn', 'Early Turn', 'Assured Fade')
`brand`	No	Filter by manufacturer/brand name (case-insensitive, alias-tolerant)
`limit`	No	Maximum number of discs to return (1..50, default 10)
`query`	No	Text query to match disc name, brand, model, or slug
`offset`	No	Pagination offset (default 0)
`category`	No	Filter by disc category (putter, midrange, fairway_driver, distance_driver)
`fade_max`	No	Maximum fade (0..6)
`fade_min`	No	Minimum fade (0..6)
`turn_max`	No	Maximum turn (-5..1)
`turn_min`	No	Minimum turn (-5..1)
`glide_max`	No	Maximum glide (1..7)
`glide_min`	No	Minimum glide (1..7)
`is_ranked`	No	If true, only return discs currently holding a global Top 100 sales ranking
`speed_max`	No	Maximum speed (1..15)
`speed_min`	No	Minimum speed (1..15)
`flight_class`	No	Filter by canonical flight class (e.g. 'understable', 'straight', 'stable', 'overstable', 'very_overstable')
`stability_max`	No	Maximum stability score (turn + fade)
`stability_min`	No	Minimum stability score (turn + fade)

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 8, 2026

changedInput schema / properties / brand / description

Previous value: -"Filter by manufacturer/brand name (case-insensitive)"New value: +"Filter by manufacturer/brand name (case-insensitive, alias-tolerant)"

addedInput schema / properties / fade_max

Added value: +{
+  "description": "Maximum fade (0..6)",
+  "type": "number"
+}

addedInput schema / properties / fade_min

Added value: +{
+  "description": "Minimum fade (0..6)",
+  "type": "number"
+}

changedInput schema / properties / flight_class / description

Previous value: -"Filter by canonical flight class (e.g. 'Early Turn', 'Progressive Turn', 'True Flight', 'Assured Fade', 'Lockdown Fade')"New value: +"Filter by canonical flight class (e.g. 'understable', 'straight', 'stable', 'overstable', 'very_overstable')"

addedInput schema / properties / glide_max

Added value: +{
+  "description": "Maximum glide (1..7)",
+  "type": "number"
+}

addedInput schema / properties / glide_min

Added value: +{
+  "description": "Minimum glide (1..7)",
+  "type": "number"
+}

addedInput schema / properties / is_ranked

Added value: +{
+  "description": "If true, only return discs currently holding a global Top 100 sales ranking",
+  "type": "boolean"
+}

addedInput schema / properties / tag

Added value: +{
+  "description": "Filter by flight tag (e.g. 'Lockdown Fade', 'True Flight', 'Progressive Turn', 'Early Turn', 'Assured Fade')",
+  "type": "string"
+}

addedInput schema / properties / turn_max

Added value: +{
+  "description": "Maximum turn (-5..1)",
+  "type": "number"
+}

addedInput schema / properties / turn_min

Added value: +{
+  "description": "Minimum turn (-5..1)",
+  "type": "number"
+}

First observedSep 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It adds genuinely useful facts — results are bounded to a 50-cap, IDs are stable, and URLs are canonical — which help an agent reason about pagination and result identity. However, it remains silent on filter combination semantics (AND vs OR), default sort order, and empty-query or no-filter behavior.

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 with zero filler. The action and scope are front-loaded in the first sentence, and the second adds the return contract. Every word earns its place; it is efficiently sized given the 18-parameter schema.

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?

For a tool with 18 optional parameters, no annotations, and no output schema, the description covers the essential return contract but omits operational details an agent would need: default sort order, whether combined filters are ANDed, pagination semantics beyond offset/limit, and behavior when no filters are supplied. Adequate but with clear gaps for a tool this complex.

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 description coverage is 100%, so the baseline is 3. The description's filter list merely paraphrases the schema's property descriptions (brand, category, speed/glide range, stability range, flight tag, flight class) without adding any new parameter-level meaning, syntax details, or interaction caveats.

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?

The description states a specific action ('Search and filter') on a clear resource ('disc golf discs') and enumerates the filter dimensions (text query, brand, category, speed/glide range, stability score range, flight tag, canonical flight class). The purpose is unmistakable and intuitively distinct from siblings like compare_discs, get_disc, or find_similar_discs, though it never names a sibling explicitly.

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?

No when-to-use guidance is provided. With 8 siblings including find_similar_discs, compare_discs, and get_disc, an agent receives no direction on which tool fits which intent, nor any exclusions, prerequisites, or conditions for choosing an alternative.

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

All TheDiscList Public MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?