Skip to main content
Glama
PinMeTo

PinMeTo Location MCP

Official
by PinMeTo

Get all locations

pinmeto_get_locations
Read-only

Retrieve all PinMeTo locations with pagination and filters like city, country, or status. Uses 5-minute caching for fast queries on large datasets.

Instructions

Get ALL locations with pagination and filtering. Uses in-memory cache (5-min TTL) for fast queries on large datasets.

Examples:

  • Get first 50 locations: {}

  • Get next page: { offset: 50 }

  • Filter by city: { city: "Stockholm", limit: 20 }

  • Only open locations: { permanentlyClosed: false }

  • Force cache refresh: { forceRefresh: true }

Error Handling:

  • Partial results may be returned on API errors (check incomplete field)

  • Stale cache data returned with warning if fresh fetch fails

  • Check errorCode (string) and retryable (boolean) in structuredContent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoFilter by city name (case-insensitive)
typeNoFilter by location type
limitNoMaximum results to return (default: 50, max: 1000)
fieldsNoFields to include in the response (optional, defaults to all)
offsetNoNumber of results to skip (default: 0)
countryNoFilter by country name (case-insensitive)
forceRefreshNoForce cache refresh (bypasses 5-minute TTL)
response_formatNoResponse format: "json" (default, token-efficient) or "markdown" (human-readable with tables)json
permanentlyClosedNoFilter by permanently closed status

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of location objects (absent on error)
errorNoError message if the request failed
limitNoRequested limit
offsetNoCurrent offset position
hasMoreNoWhether more results exist beyond offset+limit
warningNoWarning message if data may be incomplete
cacheInfoNoCache status information
errorCodeNoError code for programmatic handling
retryableNoWhether the operation can be retried
incompleteNoWhether data may be incomplete due to pagination errors
totalCountNoTotal locations matching filters
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses in-memory cache behavior with a 5-minute TTL, force refresh capability, partial result handling on API errors, stale cache fallback, and errorCode/retryable fields. This provides substantial behavioral context that the annotation alone does not 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 well-structured with clear sections for purpose, examples, and error handling. It front-loads the core purpose and keeps each section appropriately concise without redundant filler. The length is justified by the tool's complexity and the valuable usage examples.

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 list tool with 9 parameters and an output schema, the description covers pagination, filtering, caching, and error behavior comprehensively. It mentions 'incomplete field' for partial results and 'structuredContent' for error details, and because an output schema exists, it does not need to enumerate return fields. This is complete for the tool's complexity.

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?

The schema already documents all 9 parameters with 100% coverage, so the baseline is 3. The description adds value through concrete examples like 'Filter by city: { city: "Stockholm", limit: 20 }' and 'Force cache refresh: { forceRefresh: true }', which illustrate parameter combinations and real usage patterns beyond the schema descriptions.

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 'Get ALL locations with pagination and filtering,' which clearly states the action, resource, and scope. The word 'ALL' distinguishes it from the sibling tool 'pinmeto_get_location' and emphasizes its list-oriented nature.

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 provides clear examples of pagination, filtering by city, and open/closed status, giving practical usage context. However, it does not explicitly contrast with 'pinmeto_search_locations' or state when to prefer one over the other, so it falls 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PinMeTo/pinmeto-location-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server