Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

taco_bell_stores

Read-only

Find Taco Bell US restaurants near a latitude and longitude with address, hours, coordinates, and per-store capabilities. Use taco_bell_store for one known location.

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": "taco_bell_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional. 0-based page index, default 0.
latitudeYesRequired. Search center latitude.
longitudeYesRequired. Search center longitude.
page_sizeNoOptional. Stores per page, 1-50, default 10.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description nevertheless adds the meaningful constraint that results are US-only and enumerates the returned store attributes (address, hours, coordinates, per-store capabilities), which is useful scope context beyond 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.

Conciseness5/5

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

Two sentences with zero waste. The core purpose and result fields come first, and the sibling routing is placed last where it reads as a clarifying note.

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 an output schema present, the description needn't explain return values, and annotations cover safety. It is complete for a near-location store search, missing only finer behavioral notes (e.g., search radius or result ordering) that would round it out.

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 the schema already documents latitude, longitude, page, and page_size. The description only implies coordinate-based lookup and adds no syntax, format, radius, or pagination detail beyond the schema, so baseline 3 applies.

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 (find), resource (Taco Bell US restaurants), and scope (near a latitude and longitude), and explicitly names the sibling taco_bell_store as the alternative. An agent can distinguish this from the single-store lookup without opening either 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 sentence 'Use taco_bell_store for one known location' gives explicit routing to the nearest alternative and the condition that selects it. It lacks any when-not guidance for this tool itself (e.g., that it is proximity-based rather than name/address search), so it falls short of a full 5.

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

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