MapLedger

Find local businesses in Austin

search_businesses

Read-onlyIdempotent

Use when someone wants a list of local businesses in Central Austin, TX by kind (for example dentists, coffee shops, plumbers), optionally only ones with no website listed or with a phone or email. Returns name, category, address, website status and contact details, each linked to its source record. Only Central Austin is covered.

Input Schema

Name	Required	Description
`limit`	No	How many results (default 20)
`query`	No	What kind of business, for example 'dentist' or 'coffee'
`sector`	No
`contact`	No
`website`	No	missing = no website listed (social pages only or none)

Output Schema

Name	Required	Description
`more`	No	Where to see every match, when there are more than returned
`status`	Yes
`results`	Yes	Businesses: name, category, address, website status, contact details and source links
`coverage`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "coverage": {
+      "type": "string"
+    },
+    "more": {
+      "description": "Where to see every match, when there are more than returned",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Businesses: name, category, address, website status, contact details and source links",
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "enum": [
+        "ok"
+      ],
+      "type": "string"
+    },
+    "total_matches": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "status",
+    "coverage",
+    "total_matches",
+    "results"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context — the hard geographic coverage limit and that results are linked to source records — but says nothing about rate limits, result ordering, or behavior when the query matches nothing.

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 trigger followed by filter semantics and a clear coverage caveat; every clause earns its place. Slightly long as a single breath, but there is no filler.

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?

An output schema exists, so return values need not be spelled out, and zero parameters are required, lowering the burden further. Coverage limits, filter intent, and result shape are all addressed; nothing essential for a correct call 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?

With 60% schema coverage, the description compensates by explaining the query semantics ('by kind — dentists, coffee shops, plumbers') and the website/contact filters ('no website listed or with a phone or email'), including what 'missing' effectively means. Only limit and sector are left to 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 (list/search) and resource (local businesses) narrowed by geography (Central Austin, TX) and by kind. The scope is unambiguous and trivially distinguishable from the land-oriented siblings find_land and land_at.

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?

Opens with an explicit trigger: 'Use when someone wants a list of local businesses... by kind', and later states the boundary 'Only Central Austin is covered', which functions as a when-not condition. It names no alternative tool, so it stops short of a 5.

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

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

Resources

Need Help?