PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get all locations

pinmeto_get_locations

Read-only

Retrieve all locations with pagination and filters for city, country, type, and status. Includes cache refresh and field selection for optimized queries.

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

Name	Required	Description	Default
`city`	No	Filter by city name (case-insensitive)
`type`	No	Filter by location type
`limit`	No	Maximum results to return (default: 50, max: 1000)
`fields`	No	Fields to include in the response (optional, defaults to all)
`offset`	No	Number of results to skip (default: 0)
`country`	No	Filter by country name (case-insensitive)
`forceRefresh`	No	Force cache refresh (bypasses 5-minute TTL)
`response_format`	No	Response format: "json" (default, token-efficient) or "markdown" (human-readable with tables)	json
`permanentlyClosed`	No	Filter by permanently closed status

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Array of location objects (absent on error)
`error`	No	Error message if the request failed
`limit`	No	Requested limit
`offset`	No	Current offset position
`hasMore`	No	Whether more results exist beyond offset+limit
`warning`	No	Warning message if data may be incomplete
`cacheInfo`	No	Cache status information
`errorCode`	No	Error code for programmatic handling
`retryable`	No	Whether the operation can be retried
`incomplete`	No	Whether data may be incomplete due to pagination errors
`totalCount`	No	Total locations matching filters

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv4.3.0Sep 5, 2026

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"

addedOutput schema / properties / data / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv4.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses cache behavior (5-min TTL, forceRefresh), degraded response modes (partial results, stale cache with warning), and error-reporting fields (errorCode, retryable, incomplete). This gives an agent a clear picture of side effects and failure behavior for a read-only tool.

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 front-loaded with purpose, then organized into compact example bullets and a separate error-handling block. Every section contributes useful information without redundant prose.

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 low-risk read-only tool with no required parameters and an output schema, the description covers pagination, filtering, cache semantics, partial failures, and error fields. An agent has enough to invoke it correctly and interpret abnormal responses.

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 coverage is 100%, so the baseline is 3. The description adds concrete example arguments for offset, limit, city, permanentlyClosed, and forceRefresh, which helps an agent understand common calling patterns beyond the schema's individual field descriptions.

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?

The description states a clear verb and resource: get ALL locations, with pagination and filtering. This makes the tool's purpose obvious, but it does not explicitly distinguish itself from the sibling pinmeto_search_locations tool, so it stops short of full sibling differentiation.

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 first sentence implies when to use it: for fetching ALL locations with pagination/filtering, and the examples reinforce pagination and filter patterns. However, it never mentions alternatives such as pinmeto_get_location for a single location or pinmeto_search_locations for search, so when-not-to-use guidance is left to inference.

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

Deploy Server