PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get location

pinmeto_get_location

Read-only

Retrieves detailed location data for a specific store ID, including address, contact info, and network connections. Solves the need to quickly access a single store's information.

Instructions

Get details for a SINGLE location by store ID. Returns structured location data including address, contact info, and network connections.

Error Handling:

Not found (404): errorCode="NOT_FOUND" if store ID doesn't exist
Auth failure (401): errorCode="AUTH_INVALID_CREDENTIALS"
All errors: check structuredContent.errorCode and .retryable for programmatic handling

Input Schema

TableJSON Schema

Name	Required	Description	Default
`storeId`	Yes	The store ID to look up
`response_format`	No	Response format: "json" (default, token-efficient) or "markdown" (human-readable with tables)	json

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Location data from the PinMeTo API (absent on error)
`error`	No	Error message if the request failed
`errorCode`	No	Error code for programmatic handling
`retryable`	No	Whether the operation can be retried

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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"
```
- changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +{}
```
- changedOutput schema / properties / data / properties / address / additionalProperties
```
Previous value: -trueNew value: +{}
```
- changedOutput schema / properties / data / properties / contact / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / data / properties / fb / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / google / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / data / properties / location / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / data / properties / openHours / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
First observedv4.0.0Aug 10, 2026

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 a concrete error contract: 404 NOT_FOUND for unknown store ID, 401 AUTH_INVALID_CREDENTIALS for auth failures, and structuredContent.errorCode/.retryable for all errors. It also states the kind of returned data, adding behavioral context beyond structured fields.

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?

Opening sentence states purpose with the key constraint; the error-handling section is compact, scannable, and adds real value. There is no filler or redundant restating of schema content.

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 two-parameter read-only lookup with an output schema and annotations, the description covers purpose, uniqueness, return content, and error behavior. Nothing necessary for correct invocation is missing.

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?

Input schema covers 100% of parameters, documenting storeId and response_format with enums and defaults. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

Description opens with 'Get details for a SINGLE location by store ID', naming the verb, resource, and uniqueness constraint. This clearly distinguishes it from siblings like pinmeto_get_locations and pinmeto_search_locations without requiring schema inspection.

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 phrase 'SINGLE location by store ID' conveys when to use this tool: when a single known store identifier is available. It does not explicitly name sibling alternatives or exclusion conditions, so it falls just short of full routing guidance.

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

Deploy Server