Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cvs_store_locator

Find nearby CVS store locations by ZIP code, address, or coordinates. Returns address, phone, hours, services, and a pharmacy existence flag.

Instructions

CVS store locator. Returns nearby CVS store locations for a ZIP code, a free-text address/city/state, or a latitude/longitude pair: address, phone, fax, distance, and retail store hours, plus a has_pharmacy existence flag and a list of general service indicators (e.g. photo, ATM, same-day delivery). Covers general store info only -- this does not return pharmacy hours, pharmacy phone, prescription data, or any patient-specific information. zip is a 5-digit US ZIP code; alternatively supply address (a free-text location such as a city, state, or street address) or latitude and longitude together. When more than one is supplied, zip wins, then address, then latitude/longitude. Optionally narrow results to stores carrying one specific service via the service param (the same code vocabulary the response's services field uses); only one service value is accepted per request. CVS.com is only available from US/US-territory egress; a request from an unsupported region returns an upstream error rather than an empty result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNo5-digit US ZIP code, e.g. \
addressNoFree-text location -- a city, state, or street address, e.g. \
serviceNoNarrow results to stores carrying one specific service
latitudeNoLatitude, used together with longitude when zip and address are not supplied
longitudeNoLongitude, used together with latitude when zip and address are not supplied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / service / enum
      Added value: +[
+  "HH_HealthHub_Ind",
+  "MC_MinuteClinic_Ind",
+  "HS_OakStreetHealth_Ind",
+  "IM_Immunization_Ind",
+  "RX_OTCH_Ind",
+  "IM_Covax_Ind",
+  "CL_CovidTest_Ind",
+  "RX_24Hours_Ind",
+  "RX_DriveThru_Ind",
+  "RX_Pharmacy_Ind",
+  "RX_DrugDisposal_Ind",
+  "RS_24Hours_Ind",
+  "PH_Photo_Ind",
+  "RS_AcceptsWic_Ind",
+  "RS_AcceptsSnap_Ind",
+  "GN_UPSAccessPoint_Ind",
+  "RS_BOPIS_Ind",
+  "GN_YMas_Ind",
+  "BT_BeautyIRL_Ind",
+  "GN_SmileDirectClub_Ind"
+]
  2. Addedv1.16.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses the scope of returned data, the exclusions, the precedence rules for multiple inputs, the single-value constraint on the service param, and the upstream error behavior for unsupported egress regions. These are non-obvious behavioral traits an agent needs to know.

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?

The description is long but every sentence earns its place: core function, output fields, exclusions, parameter guidance, service filter semantics, and egress limitations. It is dense with useful information and contains no fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description completely covers what is returned, what is excluded, how to select parameters, how conflicts are resolved, the service vocabulary relationship, and the regional failure mode. Nothing an agent needs to call this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the conflict resolution precedence among zip/address/lat-lng, the requirement that latitude and longitude be supplied together, and the fact that only one service value is accepted per request. This extra context justifies a 4.

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 opens with a specific verb and resource ('Returns nearby CVS store locations') and enumerates the exact output fields (address, phone, fax, distance, retail store hours, has_pharmacy, service indicators). It clearly differentiates itself as a general store info tool rather than a pharmacy-data tool, which distinguishes it from any pharmacy-focused sibling.

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 description gives clear when-to-use context: it covers general store info only and explicitly states what it does NOT return (pharmacy hours, pharmacy phone, prescription data, patient-specific info). It also provides parameter precedence (zip wins, then address, then lat/long) and a geographic egress restriction. However, it does not name alternative tools the agent should use instead, so it stops short of a 5.

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