Crawlora MCP

yelp_geocode

Read-only

Geocode a free-form address into structured location data via Yelp. Credential-free: no login, no cookie required. Not business-scoped.

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": {
      "address": "<address>"
    },
    "name": "yelp_geocode"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Free-form address to geocode

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / address / description
```
Added value: +"Free-form address to geocode"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description nonetheless adds genuinely useful behavioral context the annotations don't convey: credential-free operation with no login or cookie required. It stops short of describing response shape or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no padding, and the core purpose is front-loaded before the credential and scope qualifiers. Every clause carries information an agent can act on.

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?

For a read-only, single-parameter geocode call whose annotations carry the safety profile and whose output schema covers the returned structure, the description supplies enough: source, credential requirement, and scope. Only the nature of the returned 'structured location data' is left entirely to the output schema.

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?

The single 'address' parameter is already documented at 100% schema coverage as a free-form address, and the description adds no format, example, or constraint beyond that wording. Per the baseline rule, high schema coverage with no extra param detail lands at 3.

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?

Specific verb + resource ('Geocode a free-form address into structured location data') plus the data source ('via Yelp'), which lets an agent place it apart from yelp_search and yelp_business. The added scope statement 'Not business-scoped' explicitly separates it from the other Yelp siblings.

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

Usage Guidelines3/5

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

The description implies usage (it is a plain address-to-coordinates lookup) and rules out business lookup with 'Not business-scoped', but it never names an alternative tool or a condition for choosing between, say, yelp_geocode and geocoding_lookup or yelp_search. Guidance is implied rather than stated.

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

All Crawlora MCP 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?