Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

walgreens_stores

Read-only

Walgreens stores near a latitude/longitude or a zip code, nearest first: name, address, phone, hours, and in-store services for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "walgreens_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoUS ZIP code; used when latitude/longitude are omitted
latitudeNoLatitude; provide with longitude, or provide zip instead
longitudeNoLongitude; provide with latitude, or provide zip instead

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. Changed3 schema fields changed
    • addedInput schema / properties / latitude / description
      Added value: +"Latitude; provide with longitude, or provide zip instead"
    • addedInput schema / properties / longitude / description
      Added value: +"Longitude; provide with latitude, or provide zip instead"
    • addedInput schema / properties / zip / description
      Added value: +"US ZIP code; used when latitude/longitude are omitted"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the 'nearest first' sort ordering, which is genuinely useful behavior. However it does not mention result limits, radius defaults, or coverage constraints. With annotations carrying the safety profile, this is adequately but not richly described.

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?

One front-loaded sentence: purpose, input, ordering, and returned fields, with no wasted words. Ideal size for a simple lookup tool.

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 a full output schema and annotations covering safety, the description only needs to convey input flexibility and result ordering, which it does. Minor gap: no mention of radius or result-count limits for a nearest-first search.

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% and each parameter already documents the lat/long-vs-zip alternative. The description restates that zip substitutes for coordinates but adds no syntax, format, or range detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (find/locate) and resource (Walgreens stores) with input modes and output fields. Clearly a store-locator tool, though it doesn't explicitly distinguish itself from the many other *_stores siblings beyond the brand name.

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 the two valid input modes (lat/long or zip), which is usage-relevant, but gives no when-to-use vs when-not guidance and no alternatives. Usage 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 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