Skip to main content
Glama
This connector has been deprecated

Search Pickleball Rules

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, with grounded answers or requests for clarification when available. The complete licensed rulebook is not provided.

Input Schema

NameRequiredDescriptionDefault
queryYesPickleball play scenario, rule topic or official rule number to look up.
languageNoRulebook evidence is available only in English (en).en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / description
      Previous value: -"Use en for official rulebook evidence; preserve original citations when translating the reply."New value: +"Rulebook evidence is available only in English (en)."
  2. Changed4 schema fields changed
    • 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"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real substance beyond that: it returns English evidence with edition and rule citations, can respond with grounded answers or clarification requests, and explicitly warns that the complete licensed rulebook is not provided.

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?

Three sentences, front-loaded with what is searched, followed by return behavior and the limitation. Minor redundancy between 'validated official 2026 ... under an official licensing agreement' and 'licensed rulebook' keeps it from a 5.

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?

An output schema exists, so return structure need not be explained, and the two fully documented parameters need little elaboration. The description covers scope, evidence language, citation output and the key limitation, leaving only sibling routing unaddressed.

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 both parameters are already documented, including the English-only constraint on language. The description only echoes the English-evidence limitation rather than adding syntax or format guidance, so baseline 3 applies.

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 named resource: searching the validated official 2026 USA Pickleball Rulebook. The licensed-rulebook scope sets it apart from the MYOPL help/website siblings, though it never names an alternative explicitly.

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 implied by the resource named (pickleball rules), and the schema's query description adds example lookups like play scenarios and rule numbers. There is no explicit when-not guidance and no routing to search_myopl_help or search_myopl_website for non-rulebook questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources