WRDO

Get a business

get_business

Read-onlyIdempotent

One business's public WRDO page: name, category, area, whether it is verified, and (for verified businesses) its description, address, opening hours (hours, as the business wrote them), website and menu link. Also open_now (true, false or null when hours are missing or unreadable) and reviews: WRDO's own reviews only (count, average_rating and up to 3 recent comments; never copied from Google or other sites; count 0 with a note when there are none). For one business already found; to look for businesses use search_local_businesses, and for prices use get_price_list. 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"), not an empty page. 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_business"
  }
}

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
`id`	Yes
`area`	Yes
`name`	Yes
`hours`	No
`source`	Yes
`address`	No
`reviews`	No	WRDO's own reviews only (never copied from Google or any other site).
`website`	No
`category`	Yes
`menu_url`	No
`open_now`	No	Open right now in SAST from the hours above; null when hours are missing or unreadable.
`page_url`	Yes
`verified`	Yes
`start_url`	Yes
`description`	No
`facebook_url`	No
`last_checked`	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."

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / open_now

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Open right now in SAST from the hours above; null when hours are missing or unreadable."
+}

addedOutput schema / properties / reviews

Added value: +{
+  "additionalProperties": false,
+  "description": "WRDO's own reviews only (never copied from Google or any other site).",
+  "properties": {
+    "average_rating": {
+      "type": "number"
+    },
+    "count": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    },
+    "recent": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "comment": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "date": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "rating": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "rating",
+          "comment",
+          "date"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "const": "wrdo",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "count"
+  ],
+  "type": "object"
+}

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses error behavior for unknown or malformed ids ('returns an error, not an empty page'), null semantics for open_now when hours are missing or unreadable, review sourcing limits (WRDO's own only, never copied), the count-0 case, and an explicit exclusion ('Never a phone number or email'). This is genuine behavioral context an agent cannot get from the annotations.

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 returned content, then the routing guidance, then the edge cases in a logical order. It is dense and slightly repetitive about reviews (count 0 note plus the sourcing caveat), but nearly every clause carries actionable information.

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 single-parameter, read-only lookup with an output schema, every ambiguity is resolved: what is returned, what is deliberately absent (phone/email, third-party reviews), how nulls arise, and what happens on a bad id. Nothing an agent needs to call 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% and the schema already documents the id format, its origin from search_local_businesses, non-guessability, and error-on-unknown behavior. The description restates the same points rather than adding new syntax or format detail, 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 ('One business's public WRDO page') and enumerates the exact fields returned (name, category, area, verification, hours, website, reviews). It also names the sibling that does the adjacent job ('to look for businesses use search_local_businesses'), so an agent can distinguish it without opening the schema.

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?

Explicit when-to-use ('For one business already found'), explicit alternatives for the two nearest needs ('search_local_businesses' for lookup, 'get_price_list' for prices), and an explicit prerequisite ('Takes the id from a search_local_businesses result'). Nothing is left to inference.

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.