WRDO

Start a request in WRDO

start_request

Read-onlyIdempotent

Get a link the person opens to ask WRDO for a quote, booking or order (optionally from one business). The person finishes in WRDO. This tool never books, charges or creates an account. It only starts a request: nothing is booked until the business confirms in WRDO. The result is a plain wa.me link with the request already typed in; it is not stored, has no token and does not expire. Nothing is sent or saved until the person opens it and sends the message. "what" is required; business_id is optional and must come from search_local_businesses (an unknown id returns an error).

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": {
      "what": "<what>"
    },
    "name": "start_request"
  }
}

Input Schema

Name	Required	Description
`what`	Yes	What the person needs: a kind of business or service ("plumber", "pizza") or a business name.
`when`	No	When they want it, in their words, e.g. "Saturday morning".
`business_id`	No	A WRDO business id (lbiz_…), copied from the "id" of a search_local_businesses result. Ids are not guessable; an unknown id returns an error.

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`next_step`	Yes
`start_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / business_id / description

Previous value: -"A WRDO business id from search_local_businesses (lbiz_…)."New value: +"A WRDO business id (lbiz_…), copied from the \"id\" of a search_local_businesses result. Ids are not guessable; an unknown id returns an error."

First observedOct 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: clarifies it never books/charges/creates an account, that nothing is booked until the business confirms, and that the returned wa.me link is unstored, tokenless, non-expiring, and sends nothing until opened. These are exactly the side-effect and lifecycle facts annotations can't express.

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-loaded with the purpose and what it isn't, which is good structure. Mild redundancy: 'This tool never books, charges or creates an account' is restated as 'nothing is booked until the business confirms,' wasting a sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param, fully documented, output-schema-backed tool, the description covers purpose, side effects, link lifecycle, and parameter provenance. Nothing an agent needs to invoke it correctly is missing.

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 the schema already documents all three parameters including the lbiz_ id format and error behavior. The description restates the required/optional split and the search_local_businesses provenance, adding little beyond what's already structured, so 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 artifact ('Get a link the person opens to ask WRDO for a quote, booking or order') and immediately scopes it against the sibling tools by noting the optional single-business filter. An agent can tell this is the request-initiation entry point, not a lookup like get_business or search_local_businesses.

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?

Explicitly says 'what' is required, 'business_id' is optional and must come from search_local_businesses, and that an unknown id errors — clear routing guidance toward the sibling that produces ids. It lacks explicit when-not-to-use framing (e.g., vs. get_business or get_price_list), so not a full 5.

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

All WRDO 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.