Skip to main content
Glama

Peskio

Place profile

places_get_profile
Read-onlyIdempotent

What a place is: tide regime and range, coast exposure and which wind/swell directions it is sheltered from or exposed to, distance to the nearest river mouth, nearby places and landmarks. Use for "is X sheltered from a north wind?", "big or small tides here?" and "near a river mouth?". Does not cover species, depth or dive sites.

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": {
      "placeId": "<placeId>"
    },
    "name": "places_get_profile"
  }
}

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
placeIdYesPeskio place id returned by places_search, e.g. "es:es-3108877". Never invent one.

Output Schema

NameRequiredDescriptionDefault
tideYes
coastYes
placeYes
aroundYes
schemaYes
landmarksYes
attributionYes
disciplinesYes
riverMouthKmYes
riverMouthNoteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description text. The description's contribution beyond annotations is scoping — it clarifies the profile is static geographic/coastal context rather than live conditions — but adds nothing about latency, result size, or what happens if a place lacks river-mouth data. Adequate, not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the payload contents, then usage cases, then the exclusion, which is a sensible order. But the opening clause 'What a place is:' is a soft framing that adds little, and the content list is dense enough to be unscannable in one pass; a compact enumeration would serve an agent better.

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 with only two fully documented parameters the description only needed to cover scope. It does that, including a boundary statement about what is absent (species, depth, dive sites). Missing only an explicit pointer to which sibling covers the excluded topics.

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%: placeId documents its format and provenance ('returned by places_search, never invent one') and lang documents the enum and its effect on page language. The description says nothing about either parameter, so baseline 3 applies — the schema does all the work.

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 enumerates exactly what the profile returns — tide regime and range, coast exposure, wind/swell shelter directions, distance to nearest river mouth, nearby places and landmarks — which is specific enough that an agent can distinguish it from a tides table or day-conditions tool. It never states a verb or resource name explicitly ('what a place is'), so it is slightly less crisp than a verb+resource statement, but the content list carries the meaning.

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?

It gives three concrete routing questions ('is X sheltered from a north wind?', 'big or small tides here?', 'near a river mouth?') that map cleanly onto the fields offered, plus an explicit exclusion of species, depth and dive sites. It stops short of naming a sibling tool for those excluded topics, so the agent must infer the alternative rather than being routed to it.

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