Skip to main content
Glama

Search the Wopee.io docs

wopee_search_docs
Read-onlyIdempotent

Search Wopee.io documentation to return matching setup, configuration, environment variable, integration, MCP client, CI, concept, and troubleshooting sections with page URLs before guessing.

Instructions

Search the Wopee.io documentation (docs.wopee.io, from its llms-full.txt) and return the best matching sections with their page URL. Use it for questions about setup, configuration, environment variables, integrations (Playwright, Cypress, WebdriverIO, Robot Framework), MCP clients, CI, concepts and troubleshooting, before guessing. Read-only, needs no API key, and does not touch the project. Results are cached for an hour.

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": "wopee_search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look up in the Wopee.io documentation, in plain words or exact names (e.g. 'WOPEE_PROJECT_UUID', 'cypress install plugin', 'self-healing locators').
maxResultsNoNumber of sections to return, 1 to 10. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.37.1

TDQS

A4.3/5.0
Behavior5/5

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

Adds three behavioral facts the annotations do not carry: no API key required (auth burden), it does not touch the project (blast radius), and results are cached for an hour (freshness expectation). Combined with the annotations declaring read-only, idempotent, and open-world access, an agent has a complete behavioral picture.

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?

Front-loads the verb, resource, and return shape in the first clause, then layers usage triggers and behavioral notes in a logical order with no filler sentences. It is a single dense block rather than scannable lines, which is a minor readability cost but not wasteful.

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 no output schema, the definition covers purpose, triggers, auth, side effects, and caching. The only residual gap is the granularity of the returned sections (chunk size or how many pages are surfaced), which an agent might want when composing a query.

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 the schema already documents both parameters with examples ('WOPEE_PROJECT_UUID', 'cypress install plugin') and the 1–10 range with a default of 5. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 Wopee.io documentation sourced from llms-full.txt — and specifies the return shape (best matching sections with page URL). This is clearly distinguishable from every sibling, which operate on projects, artifacts, and test data rather than documentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use triggers by naming topic areas (setup, configuration, environment variables, integrations, MCP clients, CI, troubleshooting) and an explicit "before guessing" directive. It also signals the boundary with project tools by noting it "does not touch the project," though it never names an alternative sibling or states when not to use it.

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