Skip to main content
Glama
Sign In

Disc Golf England (EDGA)

by io.github.frankbongo
OverviewDiscussionsAdmin

get_course_development_framework

Retrieves advisory EDGA course planning guidance with verified national participation baselines (UDisc partnership), source links, evidence dates and verification limits. Numerical buffers, budgets and case-study claims require local verification; they are not an authoritative safety standard.

Input Schema

NameRequiredDescriptionDefault
hole_countYesProposed number of holes/targets.
landowner_typeYesThe target landowner or managing authority.
include_case_studiesNoInclude source-reported Forestry England, Telford Town Park, or Bristol DGC figures with verification status and evidence periods.all
include_sign_off_storiesNoInclude suggested approval discussion points with their evidence limits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / include_case_studies / description
      Previous value: -"Include source-reported Forestry England or Telford figures with verification status and evidence periods."New value: +"Include source-reported Forestry England, Telford Town Park, or Bristol DGC figures with verification status and evidence periods."
    • changedInput schema / properties / include_case_studies / enum
      Previous value: -[
-  "all",
-  "forestry_england",
-  "telford_municipal",
-  "none"
-]New value: +[
+  "all",
+  "forestry_england",
+  "telford_municipal",
+  "bristol_municipal",
+  "none"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses important caveats: numerical buffers, budgets, and case-study claims require local verification and are not an authoritative safety standard. However, it doesn't describe permissions, rate limits, or output characteristics beyond the advisory nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the core retrieval purpose, and includes critical caveats without excess. It's efficient and well-structured, though slightly dense.

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 no annotations, no output schema, and 4 parameters (100% schema coverage), the description covers the advisory nature and verification limits but omits potential output format details or usage constraints. It's adequate but leaves gaps in behavioral context.

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 schema already fully documents all parameters including enums and defaults. The description adds no additional parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb (retrieves) and resource (EDGA course planning guidance) with scope detail about baselines and sources. It distinguishes itself from siblings like get_club_starter_guidance by focusing on course development and landowner-specific planning, but it doesn't explicitly name or contrast with siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for course planning with verified national baselines, but it doesn't state when to choose this over sibling tools like get_club_starter_guidance or search_courses. No explicit exclusions or alternative routing are provided.

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

All Disc Golf England (EDGA) toolsInspect
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