# MYOPL MCP tools: parameters, responses and examples | MYOPL Help Center Source: https://myopl.net/wiki/opl-intelligence/mcp-tool-reference/ Language: en Public reference excerpt. Consult the source page for complete context. MYOPL MCP tools: parameters, responses and examples Published October 10, 2026 MYOPL provides five public MCP tools and five tools for your connected account. This reference explains what to ask, which inputs each tool takes and how to read its response. For a player-friendly introduction, read What can you ask MYOPL through your AI assistant?. Choose your connection Connection Endpoint Access Public Free public lookups without a MYOPL account or API key. Personal MYOPL Plus or higher, OAuth sign-in, consent and enabled account features. Use Connect your AI for setup and OAuth connection help to connect or disconnect your account. You can ask your assistant in everyday language; developers use the exact tool and parameter names below. Tool names, JSON fields and enum values stay the same in every language. Connect directly from an AI assistant In your assistant's remote MCP settings, add MYOPL with and no authentication. Start a chat: “Use MYOPL to show the published pickleball rating for username g.” For personal tools, add , choose OAuth, sign in to your MYOPL Plus or higher account and approve the requested permissions. Ask “What is my pickleball OPL Rating?” or supply a league link and ask for your next session. Review any prepared RSVP through its MYOPL confirmation link. For supported desktop and agent clients, you can also install the public connection: Connect your own model or inference endpoint Choose a model provider, a hosted inference endpoint or a local model that fits your application. The model produces the conversation; an MCP client in your application retrieves MYOPL data. Configure these as separate connections. For example, Hugging Face Inference Endpoints hosts your chosen model. Configure its inference URL and provider credentials in your agent application's model settings, then add MYOPL in its MCP settings: Application setting Example value Model connection Your deployed Hugging Face inference URL and its provider credentials Public tools connection , Streamable HTTP, no authentication Personal tools connection , Streamable HTTP, per-user MYOPL OAuth The same separation applies when you change inference providers. Use a model and agent runtime that support tool calling, and follow this request cycle: Initialize the MCP connection and retrieve . Pass each tool's name, description and to the model in the tool format supported by its inference API. When the model requests a MYOPL tool, validate its arguments and execute through the MCP client. Return the result to the model with the matching tool-call identifier. Read against the tool's and handle before composing a successful answer. Include the MYOPL attribution and returned source links in the answer. Preserve rating precision, rule citations and the distinction between zero, unknown and unrated values. The agent runtime performs the tool calls; a model inference request alone does not execute them. Keep inference credentials with the model provider and MYOPL tokens with the MYOPL client. Personal OAuth belongs to the individual user; follow the granted scopes, refresh-token flow and rate-limit retry headers. See the integration guide, OAuth guide and MCP host/client architecture. Read the tool schemas After , call on the chosen connection. Each tool provides an with parameter descriptions and an for the data returned in . Personal tools are listed according to the account's permissions and enabled features. Call with the tool's name and arguments. For example: Read for the named fields described below and for the accompanying text. Include MYOPL and the returned MYOPL source links in answers. Card presentation information is supplied separately in ; MCP Apps clients use the referenced resource to render it. The developer guide and integration guide cover HTTP headers, discovery and client configuration. Public tools 1. get_public_player_rating Retrieve the current published singles and doubles OPL Ratings and public rating totals for an exact MYOPL username. Example question: “Show the pickleball rating and statistics for MYOPL username g.” Parameter Required Description Yes Exact public MYOPL username without . Use 1–64 letters, numbers, underscores, periods or hyphens. Example: . Returns: , , , and . When a player is found, the response also includes , , , , , , and . The rating fields are explained below. The player's unique provides the MYOPL link for connecting with that player. A single result supplies both formats and the public rating card. 2. prepare_pickleball_browse Find public courts, clubs or Open Play Leagues for a named city, state or country, or offer the user a choice of categories. Example question: “Find pickleball courts in Jupiter, Florida.” Parameter Required Description Yes City, state or country, 1–120 characters. Example: . Ask for more detail when a place name is ambiguous. No for English or for Spanish labels. Defaults to . No , , or . Omit it to receive category choices. and return public league listings. Returns: , , , , , , , , and . Each choice has , and . Status is , or . With a category, records , , and ; contains up to five listings, and indicates additional matches. Refine the location when is true. Each listing includes , , , , and . Depending on the listing, it can also contain: Place details: , , , , , , and . Court totals: , and . Linked places: or , with , , , and . League context: , and . Open to continue in MYOPL. Interpret availability and standings using the returned fields: means a directory lookup, and means the response supplies no standings link. A directory result is a place to explore; attendance is handled through the league's session and RSVP workflow. 3. search_pickleball_rules Find relevant evidence from the official 2026 USA Pickleball Rulebook, which MYOPL uses under an official licensing agreement with USA Pickleball. Example question: “Explain the kitchen-line rule on a serve and cite the official rule.” Parameter Required Description Yes Pickleball scenario, topic or official rule number, 1–1,000 characters. No Use for official rulebook evidence; defaults to . Preserve the original rule citations when translating the answer for the user. Returns: , , , , , , , , , and an when supplied. contains up to five excerpts, each with , , , , , , , and . Use and the returned source links when citing a rule. Ask the question in when present. identifies a partial excerpt; is null when contact redaction was needed, while contains the redacted excerpt. See the MYOPL pickleball rules guide for further reading. 4. search_myopl_help Find published MYOPL Help Center instructions with links to the full articles. Example question: “Find MYOPL instructions for changing my court preferences.” Parameter Required Description Yes MYOPL feature or task for which the user needs instructions, 1–1,000 characters. No for English or for Spanish. Defaults to . Returns: , , , and . Each of up to five results contains , , , and . Link to for the full article. 5. search_myopl_website Find published MYOPL product information and learning guides with source links. Example question: “Find MYOPL's explanation of rating reliability.” Parameter Required Description Yes MYOPL product or website topic to find in published pages, 1–1,000 characters. No for English or for Spanish. Defaults to . Returns: , , , and . Each of up to five results contains , , , and . Use the page's as the source link in your answer. Personal tools Personal tools use the account identified by OAuth. The following scopes describe the permission each tool requires. For a league parameter, use the exact identifier from the user's MYOPL league link: 1–150 letters, numbers, underscores or hyphens. The account must belong to that league. 6. get_my_rating Retrieve your current published singles and doubles OPL Ratings and public totals. Example question: “What is my pickleball OPL Rating?” Permission: . Parameters: None; send an empty object . OAuth identifies the player. Returns: The same rating fields as , including and . When the connection also grants statistics access, this call supplies the complete MYOPL card. Use this one result for a rating question instead of requesting a second statistics card. 7. get_my_next_session Find the next session in a MYOPL league you belong to. Example question: “When is my next session in this MYOPL league?” Share the league link. Permission: . Parameter Required Description Yes Exact MYOPL league slug from its link, for a league the connected account belongs to. Returns: , , and . Date and time are strings as displayed by MYOPL; preserve their supplied meaning when replying. 8. prepare_my_rsvp Prepare an attendance response for your next league session, then review and confirm it on MYOPL. Example question: “Prepare a Going RSVP for my next session in this league.” Permission: . Parameter Required Description Yes Exact MYOPL league slug from its link, for a league the connected account belongs to. Yes to attend, if undecided or to decline. The account owner confirms on MYOPL. Returns: , , , and . is the number of seconds remaining to confirm. Open the returned , review the proposal and confirm. Use the returned action identifier to check completion. 9. get_my_action_status Check whether MYOPL completed an RSVP you prepared and confirmed. Example question: “Did MYOPL confirm the RSVP I just approved?” Permission: . Parameter Required Description Yes The 64-character alphanumeric identifier returned by on this same account connection. Use the returned value exactly. Returns: and when supplied. Status Meaning The prepared action awaits confirmation. MYOPL is processing the confirmed action. MYOPL completed and synchronized the RSVP. The action did not complete; follow the returned guidance. No accessible, unexpired prepared action was found for this connection. Report an RSVP as completed only when its status is . 10. get_my_statistics_card Retrieve your singles and doubles statistics card and text summary. Example question: “Show my games, points and Reliability Score for pickleball.” Permission: . Parameters: None; send an empty object . OAuth identifies the player. Returns: , , , , , , , , , , , and . The response supplies the card separately in . Include the returned totals and a MYOPL source link in the text reply. Rating fields shared by the rating and statistics tools and hold the published ratings as decimal strings or null. Each and object contains: Field Type and meaning Exact decimal string, or null for an unrated format. Preserve the supplied precision. or . Number from 0 to 100, or null when unknown. Non-negative integer or null: games played in this format. , Non-negative integers or null: games won and lost. , Non-negative integers or null: points won and lost. A recorded zero is a value; null is unknown. Games are distinct from matches. If is false, use the returned text instead of constructing a rating. Request current data for each new rating question and retain MYOPL attribution. Response handling and further reading A tool execution error has and an field in ; public tool errors also include and . Transport and invalid-request errors use HTTP or JSON-RPC error responses. Honor on HTTP 429. Personal integrations renew expired access tokens using their OAuth refresh grant. MYOPL developer reference MCP transport and client setup Public OpenAPI specification Personal OpenAPI specification OAuth implementation guide Connect your AI Explore MYOPL AI tools Related Articles Use the AI Discovery API Understand who can request AI Discovery API access and how it differs from OPL Intelligence in the app. Chat with OPL Intelligence Start a direct AI chat or use @opl in a conversation when the assistant is available to your account. Manage OPL Intelligence Settings Enable or disable OPL Intelligence and review the options available to your account. Connect an AI assistant to MYOPL with OAuth Learn how to sign in, review permissions, connect an approved AI assistant to MYOPL, and resolve an incomplete or expired authorization link.