WRDO

Get a price list

get_price_list

Read-onlyIdempotent

A business's price list or menu, for any kind of business (salon, barber, nails, beauty, restaurant): sections of items with name, description, price_zar (rand) and, for services, duration_min. prices_confirmed is false (with a price_note) when the prices come from the business website and are not confirmed. For a business already found (has_price_list is true in search_local_businesses); it is not a search and gives no business details (use get_business). Takes the id from a search_local_businesses result. An unknown or malformed id returns an error ("WRDO has no public business with that id"); a known business with no list returns empty sections. Never a phone number or email.

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": {
      "id": "<id>"
    },
    "name": "get_price_list"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	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
`source`	Yes
`message`	No
`business`	Yes
`page_url`	Yes
`sections`	Yes
`truncated`	Yes
`item_count`	Yes
`price_note`	No
`prices_confirmed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / 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.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the error contract for unknown or malformed ids, the empty-sections outcome for a known business without a list, and the prices_confirmed=false + price_note caveat for website-sourced prices. It also clarifies the response never contains phone or email, which shapes downstream expectations.

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 resource and its contents, then constraints and edge cases in a logical order; every clause carries information. It is a dense single paragraph and the parenthetical business-type list (salon, barber, nails, beauty, restaurant) is slightly redundant, keeping it from a 5.

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?

With an output schema present the field-level return details need not be repeated, yet the description still covers error and empty-result behavior plus the price-confirmation caveat. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents id, so the schema carries the baseline. The description reinforces the semantics by tying the id to a search_local_businesses result and noting an unknown or malformed id returns an error, adding a small amount of usage meaning beyond the schema.

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 ('A business's price list or menu') and enumerates the exact payload (sections of items with name, description, price_zar, duration_min). It explicitly distinguishes itself from siblings by declaring 'it is not a search and gives no business details (use get_business).'

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

Usage Guidelines5/5

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

Gives a precise precondition ('For a business already found (has_price_list is true in search_local_businesses)'), names where the id comes from, and routes the agent to get_business for details and search_local_businesses for discovery. When-not-to-use is stated explicitly.

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.