MYOPL Pickleball

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/net.myopl/pickleball-public-knowledge

Search MYOPL Help

search_myopl_help

Read-onlyIdempotent

Search published MYOPL Help Center articles by feature or task. Returns matching instructions and source links without accessing accounts or conversations.

Input Schema

Name	Required	Description	Default
`query`	Yes	MYOPL feature or task for which the user needs instructions.
`language`	No	Language for MYOPL content and labels: en for English or es for Spanish.	en

Output 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_myopl_help."

addedInput schema / properties / language / description

Added value: +"Language for MYOPL content and labels: en for English or es for Spanish."

addedInput schema / properties / query / description

Added value: +"MYOPL feature or task for which the user needs instructions."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "MYOPL structured response for search_myopl_help.",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "clarification": {
+          "description": "Follow-up question when more detail is needed, otherwise null.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "guidance": {
+          "description": "Citation and source interpretation instructions.",
+          "type": "string"
+        },
+        "myopl_url": {
+          "description": "MYOPL website.",
+          "format": "uri",
+          "type": "string"
+        },
+        "results": {
+          "description": "Matching MYOPL pages; empty when no page matches.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "excerpt": {
+                "description": "Matching passage from the page.",
+                "maxLength": 1800,
+                "type": "string"
+              },
+              "language": {
+                "description": "Language of the response.",
+                "enum": [
+                  "en",
+                  "es"
+                ],
+                "type": "string"
+              },
+              "title": {
+                "description": "Page title.",
+                "type": "string"
+              },
+              "truncated": {
+                "description": "True when the excerpt is only part of the source page.",
+                "type": "boolean"
+              },
+              "url": {
+                "description": "Published MYOPL page to cite.",
+                "format": "uri",
+                "type": "string"
+              }
+            },
+            "required": [
+              "url",
+              "title",
+              "language",
+              "excerpt",
+              "truncated"
+            ],
+            "type": "object"
+          },
+          "maxItems": 5,
+          "type": "array"
+        },
+        "source": {
+          "description": "Published source collection.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "source",
+        "myopl_url",
+        "results",
+        "clarification",
+        "guidance"
+      ],
+      "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 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it states the search is limited to published help articles and that it operates 'without accessing accounts or conversations', which tells the agent this is a privacy-safe, corpus-bounded lookup rather than a live account query.

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?

Two compact sentences with zero filler: the first establishes what is searched and over what scope, the second establishes the return shape and the privacy boundary. The most decision-relevant information is front-loaded.

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?

For a two-parameter read-only lookup with a full output schema and rich annotations, the description covers purpose, scope and return shape adequately. The one missing piece is routing guidance relative to 'search_myopl_website' and 'search_pickleball_rules', which would matter for an agent choosing among sibling search tools.

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 'query' and 'language' are already documented, and the description only restates the 'feature or task' framing of the query parameter. It says nothing about the 'language' parameter (en/es) or about query phrasing/length, so no meaning is added beyond the schema.

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 names a specific verb and resource ('Search published MYOPL Help Center articles') and scopes it to 'by feature or task', so the agent knows what corpus is being queried. It does not, however, distinguish itself from the sibling 'search_myopl_website', leaving the agent to infer why one search surface is preferred over the other.

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 clearly enough — the tool is for finding instructions on a MYOPL feature or task — but there is no explicit when-to-use framing, no prerequisites, and no mention of the sibling search tools as alternatives. The agent must infer routing from the name alone.

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

All MYOPL Pickleball 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?