MYOPL MCP Server - Official Pickleball Rules & Ratings

search_pickleball_rules

Read-onlyIdempotent

Search the validated official 2026 USA Pickleball Rulebook, used by MYOPL under an official licensing agreement with USA Pickleball. Returns English evidence, edition and rule citations, plus a grounded answer when the private resolver is enabled. Preserve requests for clarification; excerpts alone do not establish a complete ruling. No package download.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Pickleball play scenario, rule topic or official rule number to look up.
`language`	No	Use en for official rulebook evidence; preserve original citations when translating the reply.	en

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 10, 2026

addedInput schema / description

Added value: +"Arguments for search_pickleball_rules."

addedInput schema / properties / language / description

Added value: +"Use en for official rulebook evidence; preserve original citations when translating the reply."

addedInput schema / properties / query / description

Added value: +"Pickleball play scenario, rule topic or official rule number to look up."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "MYOPL structured response for search_pickleball_rules.",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "answer": {
+          "description": "Grounded answer with rule citations when supplied.",
+          "type": "string"
+        },
+        "clarification": {
+          "description": "Required clarification of the play, or null.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "edition": {
+          "description": "Rulebook edition year as a string.",
+          "type": "string"
+        },
+        "evidence": {
+          "description": "Up to five cited rule excerpts.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "authority": {
+                "description": "Authority classification of the source record.",
+                "type": "string"
+              },
+              "canonical_url": {
+                "description": "MYOPL rulebook guide citation URL.",
+                "format": "uri",
+                "type": "string"
+              },
+              "canonical_url_type": {
+                "const": "rulebook_guide",
+                "description": "Identifies the linked source as a rulebook guide.",
+                "type": "string"
+              },
+              "official_text": {
+                "description": "Verbatim rule excerpt, or null if contact redaction was required.",
+                "maxLength": 4000,
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "rule": {
+                "description": "Rule identifier.",
+                "type": "string"
+              },
+              "rule_number": {
+                "description": "Official rule identifier for citation.",
+                "type": "string"
+              },
+              "text": {
+                "description": "Rule excerpt with contact details redacted where necessary.",
+                "maxLength": 4000,
+                "type": "string"
+              },
+              "title": {
+                "description": "Rule title.",
+                "type": "string"
+              },
+              "truncated": {
+                "description": "True when the excerpt is shorter than the source rule.",
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "rule",
+              "rule_number",
+              "official_text",
+              "canonical_url",
+              "canonical_url_type",
+              "title",
+              "text",
+              "truncated",
+              "authority"
+            ],
+            "type": "object"
+          },
+          "maxItems": 5,
+          "type": "array"
+        },
+        "governing_body": {
+          "description": "Organization responsible for the rulebook.",
+          "type": "string"
+        },
+        "guidance": {
+          "description": "Instructions for preserving citations, exceptions and clarification questions.",
+          "type": "string"
+        },
+        "language": {
+          "description": "Language of the rulebook evidence.",
+          "type": "string"
+        },
+        "myopl_url": {
+          "description": "MYOPL rulebook guide to cite.",
+          "format": "uri",
+          "type": "string"
+        },
+        "source": {
+          "description": "MYOPL rule evidence source.",
+          "type": "string"
+        },
+        "source_url": {
+          "description": "Governing body's official rulebook page.",
+          "format": "uri",
+          "type": "string"
+        },
+        "spoken_reply": {
+          "description": "Rule response with MYOPL attribution and citation link.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "source",
+        "governing_body",
+        "edition",
+        "language",
+        "source_url",
+        "myopl_url",
+        "evidence",
+        "clarification",
+        "guidance",
+        "spoken_reply"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "description": "Tool execution or argument error; the enclosing result has isError set to true.",
+          "type": "string"
+        },
+        "myopl_url": {
+          "description": "MYOPL website.",
+          "format": "uri",
+          "type": "string"
+        },
+        "source": {
+          "const": "MYOPL",
+          "description": "Source platform.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "error",
+        "source",
+        "myopl_url"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add context - and it does: conditional grounded answers when the private resolver is enabled, English-only evidence, citation output, the caveat that excerpts are not a complete ruling, and a 'no package download' constraint.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, which is a strength. However, the middle sentence mixes return-value and feature-flag details, and the trailing clauses ('Preserve requests for clarification', 'No package download') are cryptic and underspecified rather than tight.

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?

With an output schema, full schema coverage, and rich annotations, the description only needs to supply differentiating scope and behavioral caveats - it provides those, including source licensing, answer-mode conditions, and the evidentiary limitation on excerpts. The unexplained 'private resolver' and 'no package download' references keep it short of complete.

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% and both parameters are documented in the schema, including the language enum, so this is the baseline case. The description adds little parameter-level detail beyond echoing that evidence is returned in English, which is closer to output behavior than parameter semantics.

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 and resource: search the validated official 2026 USA Pickleball Rulebook, naming the licensor. That scope is clearly distinct from generic siblings like search_myopl_website or search_myopl_help, though the description never explicitly contrasts itself with them.

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?

Usage is only implied: an agent infers this is the tool for rules questions, but there is no statement of when to prefer it over search_myopl_help, search_myopl_website, or prepare_pickleball_browse, and no prerequisites or exclusions.

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

All MYOPL MCP Server - Official Pickleball Rules & Ratings 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?