Skip to main content
Glama

Détails d’un centre

get_center_details
Read-onlyIdempotent

Details of one centre: address, phone, opening hours (Paris time), upcoming closures, accepted payment methods (online / on site / card-only), free parking hours, whether it is open now and bookable today, and its vehicle price categories (s/m/l/xl/van/moto) with example models — prices depend on the category. Fields prefixed untrusted* are text written by the centre operator.

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": {
      "centerSlug": "<centerSlug>"
    },
    "name": "get_center_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
centerSlugYesCentre slug as returned by find_centers or search_available_slots

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 safety is covered; the description adds real value beyond them by stating that hours are in Paris time, that prices are category-dependent, and that untrusted*-prefixed fields are operator-written text (a useful prompt-injection warning). It stops short of saying what happens for an unknown or stale slug.

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

Conciseness4/5

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

Front-loaded with the resource and resource-scoped, with every clause contributing a distinct returned field. The single long sentence is dense but slightly run-on, packing payment methods, parking, availability and pricing into one breath.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so thoroughly — enumerating each field group, noting timezone, category-dependent pricing, and the untrusted-data convention. For a single-parameter read tool this is complete enough to call correctly.

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 100%: the single centerSlug parameter carries its own description, regex pattern and source guidance (find_centers / search_available_slots). The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific resource ('Details of one centre') and enumerates the concrete content returned: address, phone, opening hours in Paris time, closures, payment methods, parking, open-now status and price categories. An agent knows exactly what this returns; the only gap is that it does not explicitly contrast itself with find_centers or search_available_slots, which are only referenced inside the schema.

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?

Usage is implied rather than stated: the schema notes the slug comes from find_centers or search_available_slots, which suggests the lookup-after-discovery pattern, but the description itself gives no when-to-use or when-not-to-use guidance and names no alternative.

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