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). Takes an id as returned by search_local_businesses. Never a phone number or email.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	A WRDO business id from search_local_businesses (lbiz_…).

Output Schema

TableJSON 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.

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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/destructive=false, and the description adds non-obvious behavior: open_now can be null when hours are missing or unreadable, review count is 0 with a note when empty, reviews are never sourced from Google, and phone/email are never returned. Much of the remaining text enumerates return fields already covered by the output schema, which slightly dilutes the behavioral value.

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?

It is one dense sentence heavy with parentheticals, but the resource is front-loaded and every clause carries factual payload (null semantics, review provenance, exclusions) rather than filler. Slightly harder to scan than an ideally structured description.

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?

With annotations carrying the safety profile and an output schema present, the description only needs to cover provenance and edge behavior, which it does (id source, null open_now, zero-review note, no phone/email). It stops short of describing failure behavior for an unknown or malformed id.

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 single id parameter already documents its format ('lbiz_…') and origin. The description's 'Takes an id as returned by search_local_businesses' restates that provenance rather than adding new syntax or constraint detail, so the baseline 3 is appropriate.

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+resource up front ('One business's public WRDO page') and enumerates exactly what that resource contains. It also distinguishes itself from the sibling search_local_businesses by naming it as the source of the id, so an agent can tell the two apart without opening a schema.

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?

The clause 'Takes an id as returned by search_local_businesses' establishes the required upstream workflow and implicitly routes the agent to the search tool first. There is no explicit when-not guidance (e.g. what to do if the page is not found), but the usage context is clear.

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.