Skip to main content
Glama

Get Place

get_place
Read-onlyIdempotent

Get one SportPoint place (gym, pool, hall, venue) by slug (from search_clubs_and_places): address, description, and one Monday-to-Sunday week of the sessions held there with price in EUR and spots left. Pass week as any date (YYYY-MM-DD) in the wanted week; the default is the current week.

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": {
      "slug": "<slug>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe place slug, as returned by search_clubs_and_places.
weekNoAny date (YYYY-MM-DD) in the week to show. Defaults to the current week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful context by describing the returned payload and the week-default behavior, but is silent on invalid/unknown slug handling and on how large the session week payload can get.

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?

Two dense sentences with the resource identification front-loaded, then return contents, then parameter semantics. No filler, no restatement of the title, and every clause carries information an agent can act on.

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?

With no output schema, the description carries the burden of explaining returns and does so concretely (address, description, weekly sessions with price and spots left), plus it explains slug sourcing and week defaults. Minor omissions like error behavior on a bad slug or session-list size keep it short of a 5.

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% and both parameters are documented there, including the slug provenance and the week date format. The description restates the same week semantics (any date within the wanted week, current week by default) without adding new constraints or examples, so it only matches the schema rather than extending it.

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?

States a specific verb and resource ("Get one SportPoint place"), enumerates the place types covered (gym, pool, hall, venue), and spells out the payload: address, description, and a Monday-to-Sunday week of sessions with EUR price and spots left. That is enough for an agent to distinguish it from search_clubs_and_places or get_club without opening a schema.

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?

Explicitly routes the agent to search_clubs_and_places as the source of the slug, which implies the use case (fetch full details for one place found via search). It does not state when *not* to use it, or contrast it against sibling get_club/get_coach, but the entry condition is clear.

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