TheDiscList Public MCP

search_discs

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

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	No	Filter by manufacturer/brand name (case-insensitive)
`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)
`speed_max`	No	Maximum speed (1..15)
`speed_min`	No	Minimum speed (1..15)
`flight_class`	No	Filter by canonical flight class (e.g. 'Early Turn', 'Progressive Turn', 'True Flight', 'Assured Fade', 'Lockdown Fade')
`stability_max`	No	Maximum stability score (turn + fade)
`stability_min`	No	Minimum stability score (turn + fade)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It implies a read-only search with no side effects, which is sufficient, though it could explicitly state that no modifications occur.

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?

A single, concise sentence that captures the full scope of the tool without unnecessary elaboration.

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?

The description mentions return limits (up to 50) and result characteristics (stable IDs, canonical URLs), which provides useful context. It lacks an output schema, but that is not required for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 10 parameters are described with meaningful details (e.g., ranges, examples for flight_class). The descriptions add clarity beyond the parameter names, fully covering the schema.

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 it searches and filters disc golf discs by multiple criteria, distinguishing it from sibling tools like compare_discs, find_similar_discs, and get_disc.

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?

While not explicitly stating when to use this over siblings, the action of searching/filtering is obvious from the description and complements the other tools' specific purposes.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct task: search_discs for discovery, get_disc for single-disc details, compare_discs for side-by-side analysis, and find_similar_discs for replacements. There is minimal risk of an agent selecting the wrong tool.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: compare_discs, find_similar_discs, get_disc, search_discs. No mixed conventions or vague verbs.

Tool Count5/5

Four tools is a tight, well-scoped set for a read-only disc golf reference server. Each tool earns its place and there is no redundancy.

Completeness5/5

The server covers the full reference workflow: search for discs, retrieve details, compare discs, and find similar alternatives. No significant lifecycle gaps exist for a public read-only database.

Resources

Need Help?