Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

arbys_directory

Find Arby's US stores by browsing state and city directories; returns store counts, city lists, or store IDs, addresses, and phone numbers without needing coordinates.

Instructions

Browse Arby's US store directory by state and city. Returns one level of Arby's US store directory: every state Arby's serves with its store count (no params), one state's cities (state given), or one city's stores (state and city given) -- id, address, and phone only, pair with GET /arbys/location for hours/amenities/status. Unlike GET /arbys/locations, this needs no coordinate; it is a plain browse of the whole ~3,200-store US chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional. City name, requires state. Omit to list every city in the state.
stateNoOptional. Two-letter US state abbreviation. Omit to list every state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return fields (id, address, phone) and points to arbys/location for hours/amenities/status, and mentions the ~3,200-store scale. It implies read-only browsing but doesn't explicitly state read-only or pagination, though 'browse' implies read-only.

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?

The description is slightly long but each sentence carries useful information: purpose, three modes, fields returned, and sibling contrast. It's front-loaded with the core purpose and efficiently packages the details.

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 simple directory tool with optional params, the description covers output levels, fields, and relationship to a sibling. It doesn't mention pagination or rate limits, but those aren't expected for a one-level browse. It's complete enough for an agent to invoke correctly.

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 coverage is 100% with both parameters well-documented in the input schema. The description reiterates the behavior but adds little beyond the schema's descriptions. It does clarify the three output levels, but that's already implied by the schema. Baseline 3 is appropriate.

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?

The description states a specific verb 'Browse' with resource 'Arby's US store directory' and explains the three levels of output based on parameters. It clearly differentiates from the sibling GET /arbys/locations by noting it needs no coordinate and is a plain browse of the whole chain.

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

Usage Guidelines5/5

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

It explicitly contrasts with arbys/locations, stating this tool is for browsing by state/city without coordinates. It also explains the parameter hierarchy: no params returns states, state returns cities, state+city returns stores. This gives clear when-to-use guidance.

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

Deploy Server

Other Tools