Skip to main content
Glama
Sign In

WRDO

by za.co.wrdo
OverviewDiscussionsAdmin

List areas

list_areas
Read-onlyIdempotent

The towns and suburbs in the Western Cape where WRDO has listings, each with its region and how many businesses (suburbs counted in their town). Gives the valid names for "where" in search_local_businesses and list_categories. Optional "query" keeps areas whose name or region contains it (e.g. "paarl" or "winelands"). Most businesses first, up to 100; areas with none are left out. Western Cape only. Names and counts only: no business or contact details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a town, suburb or region name, e.g. "paarl" or "cape town". Leave out for every area.

Output Schema

NameRequiredDescriptionDefault
areasYes
totalYesHow many areas match, before the cap on this list.
sourceYes
messageNo
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, yet the description still adds ordering ('most businesses first'), a hard cap ('up to 100'), an exclusion rule ('areas with none are left out'), and a data-boundary statement ('no business or contact details'). These are real behavioral facts not derivable 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-loaded with the resource definition and packed with substance; each clause (routing, query, ordering, cap, scope, output shape) carries information. It is a single dense block rather than clearly segmented, which costs a point but nothing is wasted.

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 a rich output schema, full parameter coverage and strong annotations, the only things an agent needs are scope, ordering, the 100-item cap and the exclusion of empty areas — all present. Nothing material is missing for correct invocation.

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%, so the baseline is 3, but the description explains substring matching against both name and region and supplies a region example ('winelands') that the schema's examples (both town names) do not cover. It also clarifies that omitting the query returns everything, reinforcing the optionality.

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 resource (towns/suburbs in the Western Cape where WRDO has listings) with its payload (region and business counts). It also names its downstream consumers, search_local_businesses and list_categories, which separates it cleanly from every sibling tool.

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 line 'Gives the valid names for "where" in search_local_businesses and list_categories' tells the agent when this tool is the right entry point, and 'Western Cape only' sets a hard scope boundary. It stops short of an explicit negative case, but the routing intent is unambiguous.

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

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

Resources