Skip to main content
Glama

Peskio

Find a place

places_search
Read-onlyIdempotent

Resolve a town, beach, harbour or cove name to Peskio placeIds (Europe, North Africa and US coasts). Call this first whenever the user names a place, then pass the placeId to the other tools. candidates[0] is the best match: when ambiguous is false, use it without asking (a harbour or beach listed after a town of the same name is part of that place). Ask which one the user means only when ambiguous is true (the same name in different regions). Never ask the user for coordinates.

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": "places_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoThe user's language (ISO 639-1; one of Peskio's 15, otherwise 'en'). Picks the peskio.com page language and local place names; answer in the user's language yourself.en
limitNo
queryYesThe place name as the user wrote it, optionally with its region.
countryNoISO 3166-1 alpha-2 code, lower case, to restrict to one country.

Output Schema

NameRequiredDescriptionDefault
exactYesA candidate carries the searched name (in any of its languages) and it is candidates[0]. false = Peskio does not have that place; candidates are only similar names.
schemaYes
ambiguousYestrue = ask the user which candidate they mean (same name in different regions, or no exact match).
candidatesYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral detail: candidates are ordered with candidates[0] as best match, harbour/beach listings fold into a same-named town, and user clarification is required only across regions. It doesn't discuss no-result or empty-candidate behavior, which keeps it below 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?

Four tight sentences, front-loaded with the purpose and workflow position, then disambiguation policy in descending order of specificity. No filler or restatement of the title.

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?

An output schema exists, so return-value explanation is not required, and the description covers resolution, ID hand-off and disambiguation. What remains unstated is behavior on zero candidates and what `limit` controls in ranking terms, minor gaps for an otherwise complete lookup tool.

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 75% and the schema already documents `query`, `lang` and `country` with defaults and patterns. The description adds no meaning for `limit` (default 5, max 10) or for how to construct the query string beyond the name, so it does not compensate for the remaining gap. 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?

The description states a specific verb and resource: resolve a town, beach, harbour or cove name to Peskio placeIds, and names the geographic scope (Europe, North Africa, US coasts). It is clearly distinguishable from siblings such as places_get_profile, which presumably consumes the placeId produced here.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to call this first whenever the user names a place and to pass the placeId to the other tools, establishing its position in the workflow. It also gives a concrete when-to-ask rule (only when `ambiguous` is true) and an explicit never-do (never ask the user for coordinates).

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