Skip to main content
Glama
This connector has been deprecated

Search MYOPL Website

search_myopl_website
Read-onlyIdempotent

Search published MYOPL product and website information by topic. Returns matching public pages and source links without accessing accounts or conversations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_myopl_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesMYOPL product or website topic to find in published pages.
languageNoLanguage for MYOPL content and labels: en for English or es for Spanish.en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / description
      Added value: +"Arguments for search_myopl_website."
    • 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 product or website topic to find in published pages."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "MYOPL structured response for search_myopl_website.",
      +  "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"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description does add one genuine behavioral fact beyond that: it only reads published public pages and does not touch accounts or conversations. It says nothing about pagination, result limits, or whether an empty result is possible, so the added context is useful but thin.

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 sentences, front-loaded with purpose before the scope boundary, and every clause carries information. No filler or restatement of the tool name.

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 search tool with full annotation coverage and an output schema that documents return values, the description covers what and scope adequately. The one meaningful gap is sibling disambiguation against search_myopl_help, which shares the 'MYOPL' domain and would benefit from an explicit routing sentence.

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%, with both the query and the en/es language enum documented with defaults. The description adds no meaning beyond the schema — no query syntax, no guidance on whether to pass language when the topic is ambiguous. Baseline 3 applies when the schema carries the 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: searches published MYOPL product and website information by topic, returning matching public pages and source links. It scopes the resource to public website content, which implicitly separates it from account/conversation data, but it never names the adjacent siblings search_myopl_help or search_pickleball_rules, so the boundary between two 'search_*' tools remains for the agent to infer.

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 phrase 'by topic' and 'published MYOPL product and website information' implies when this tool applies, and the exclusion of accounts/conversations narrows scope. However, there is no explicit rule for choosing this over search_myopl_help, no statement of what input phrasing works best, and no when-not-to-use guidance.

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