Crawlora MCP

sonic_nearby

Read-only

Sonic Drive-In restaurants near a latitude/longitude, nearest first, with distance in miles plus full store detail per result.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "sonic_nearby"
  }
}

Input Schema

Name	Required	Description
`page`	No	Zero-based page number. Defaults to 0.
`limit`	No	Stores per page, 1-50. Defaults to 10.
`radius`	No	Search radius in miles, 1-100. Defaults to 25.
`latitude`	Yes	Required. Latitude of the search centre, -90 to 90.
`longitude`	Yes	Required. Longitude of the search centre, -180 to 180.

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.

First observedOct 7, 2026

TDQS

A3.6/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 adds genuine behavioral detail beyond that: results are ordered nearest-first, distances are expressed in miles, and each result carries full store detail. It stops short of noting pagination or radius defaults, which the schema supplies.

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?

A single sentence that front-loads the resource and the locational input, then appends ordering and return-shape detail. No filler or redundancy.

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 nearby-search tool with an output schema and fully documented parameters, the description covers what it does, how results are ordered, and what each result contains. The missing piece is routing guidance against the many overlapping Sonic location tools.

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%, so page, limit, radius, latitude, and longitude are all documented in the schema itself. The description adds no formatting or constraint detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Sonic Drive-In restaurants near a latitude/longitude') and adds scope (proximity search, nearest-first ordering). This implicitly separates it from directory-style siblings like sonic_locations or sonic_directory, but no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this tool over sonic_locations, sonic_directory, sonic_store, or sonic_location_suggest, and no conditions or exclusions are given. The only hint is the proximity framing, which the agent must infer.

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.