Skip to main content
Glama

Search Locations by Name

skimguard_search_locations
Read-onlyIdempotent

Find a location by NAME or address (e.g. "Shell on Riverside, Austin TX", "Chase ATM near Union Square") and get its SkimGuard card-skimmer scan status. Use this when you know what a place is called but do not have its Google Place ID — it resolves the name first, then reports scan status for each match. Pass latitude/longitude when you know roughly where the user is; it sharply improves matching for common brand names. Locations with no scan data are reported as unknown, never as unsafe.

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": {
      "query": "<query>"
    },
    "name": "skimguard_search_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (1-365, default 30)
limitNo
queryYesPlace name and ideally a city, e.g. "Shell gas station Riverside Austin TX"
latitudeNoOptional bias — the user's approximate latitude
longitudeNoOptional bias — the user's approximate longitude
response_formatNoResponse format: 'markdown' (default) or 'json'markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety bar is met; the description goes further by explaining the two-stage behavior (resolve name, then report status per match) and the critical semantics that no scan data means unknown, never unsafe. It omits anything about result volume beyond the limit cap or latency/rate behavior, keeping it short of a 5.

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 core action and the name-vs-Place-ID distinction are front-loaded in the first two sentences, with the parameter advice and the unknown-vs-unsafe caveat following in order of importance. Every sentence carries distinct information; nothing restates the title or schema.

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 no output schema, the description takes on the burden of describing results and does so adequately (per-match scan status, unknown handling). For a read-only lookup with 83% schema coverage this is nearly complete; only the shape of a match record and pagination/limit behavior are left implicit.

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 83%, so the schema already documents all six parameters including ranges and defaults. The description adds real value for latitude/longitude by explaining why to supply them ("sharply improves matching for common brand names"), but says nothing extra about days, limit, or response_format, so it stays near the high-coverage baseline.

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 and resource ("Find a location by NAME or address") plus the payload it returns ("SkimGuard card-skimmer scan status"), with concrete example queries. It also distinguishes itself from the alternative path: it resolves a name rather than requiring a Google Place ID, which separates it from the status-by-ID 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?

Explicitly says when to use it: "Use this when you know what a place is called but do not have its Google Place ID." It also advises passing latitude/longitude when approximate position is known. It does not name the sibling tool to use instead when a Place ID is available, leaving that last routing step to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources