Skip to main content
Glama
PinMeTo

PinMeTo Location MCP

Official
by PinMeTo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search locations

pinmeto_search_locations
Read-only

Search locations by name, address, store ID, or descriptor to quickly find matching places. Use returned store IDs to retrieve full details when needed.

Instructions

Search ALL locations by name, address, store ID, or location descriptor. Returns lightweight results for quick discovery. Use pinmeto_get_location with storeId for full details.

Error Handling:

  • Network issues: errorCode="NETWORK_ERROR", retryable=true

  • Auth failure (401): errorCode="AUTH_INVALID_CREDENTIALS"

  • All errors: check structuredContent.errorCode and .retryable for programmatic handling

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 20, max: 100)
queryYesSearch query - matches against name, storeId, locationDescriptor, street, city, or country
response_formatNoResponse format: "json" (default, token-efficient) or "markdown" (human-readable with tables)json

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoMatching locations with minimal data for discovery (absent on error)
errorNoError message if the request failed
hasMoreNoWhether more results exist beyond the limit
errorCodeNoError code for programmatic handling
retryableNoWhether the operation can be retried
totalMatchesNoTotal number of locations matching the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.3.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv4.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true. The description adds meaningful behavior: results are lightweight, errors use structuredContent.errorCode and .retryable, and specific error codes for network and auth failures are provided. This goes beyond what the annotations convey.

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 compact and front-loaded with the core purpose, then quickly gives the alternative for full details and structured error handling. Every sentence earns its place.

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 search tool with readOnlyHint, full schema coverage, and an output schema, the description covers purpose, result nature, alternative use, and error handling. Nothing essential is missing for correct invocation and response interpretation.

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 query, limit, and response_format in detail. The description restates the search fields but does not add new parameter semantics beyond the schema.

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 ('Search') and resource ('ALL locations'), with clear searchable fields: name, address, store ID, and location descriptor. It further distinguishes itself by noting lightweight results and directing to pinmeto_get_location for full details.

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 explicitly tells the agent to use pinmeto_get_location with storeId when full details are needed, providing a clear alternative. It does not explicitly discuss when to use pinmeto_get_locations, but the search-versus-retrieve distinction is reasonably clear.

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