DiscGolfAPI MCP

search_courses

Search for disc golf courses by name, city, country, region, hole count, or features.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (1-25, default: 10).
`query`	No	Text search query for course name, city, or keywords (1-200 characters).
`offset`	No	Pagination offset (0-1000, default: 0).
`region`	No	State, province, or region code/name (e.g. 'FL', 'OR', 'England').
`country`	No	ISO 3166-1 alpha-2 country code (e.g. 'US', 'GB', 'FI') or country name.
`is_free`	No	Filter to free-to-play public courses.
`is_18_holes`	No	Filter to courses with 18 or more holes.
`is_pay_to_play`	No	Filter to pay-to-play or commercial courses.
`is_dog_friendly`	No	Filter to dog-friendly courses.
`has_multiple_pins`	No	Filter to courses with multiple basket/pin positions.
`has_multiple_tees`	No	Filter to courses with multiple tee pads per hole.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool searches, with no information about result ordering, filter combination behavior, pagination, or any limitations. The read-only nature is implied by the name but not stated.

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 a single front-loaded sentence with no filler. Every word contributes to the core purpose, and it remains easy to parse.

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?

The schema documents all 11 parameters well, but the description is thin for a tool with no annotations and no output schema. It does not explain how filters combine, what the response looks like, or how this tool relates to find_courses_near, leaving some gaps for an agent.

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 parameters are already well documented. The description's list of searchable criteria adds a high-level summary but does not clarify how the boolean feature filters map to 'hole count' or 'features' beyond what the schema provides.

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 uses a specific verb ('Search') and identifies the resource ('disc golf courses') plus the main search dimensions. It is clear, but it does not explicitly differentiate from the sibling tool find_courses_near.

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 gives clear context about when to use the tool: when searching by name, city, country, region, hole count, or features. However, it does not mention alternatives or exclusions, such as when to prefer find_courses_near for location-based searches.

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

All DiscGolfAPI 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?