Skip to main content
Glama

Rechercher des kinésithérapeutes autour d'un point

rechercher_kines_autour
Read-onlyIdempotent

Recherche des masseurs-kinésithérapeutes inscrits sur MonRdvKiné autour de coordonnées GPS (position du patient, adresse géocodée). Renvoie au plus 20 praticiens, du plus proche au plus éloigné, avec DistanceKm (à vol d'oiseau), AcceptsNewPatientsOnline et IsQueueListActive. Utiliser ensuite disponibilites_nouveau_patient avec PhysicianId.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "rechercher_kines_autour"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude en degrés décimaux, par exemple 45.7578.
rayon_kmNoRayon de recherche en km (10 par défaut, 50 au maximum).
longitudeYesLongitude en degrés décimaux, par exemple 4.8320.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: results are capped at 20, sorted nearest to farthest, DistanceKm is straight-line distance, and the key flags returned (AcceptsNewPatientsOnline, IsQueueListActive). What happens when more than 20 practitioners match within the radius is not stated.

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?

Three dense sentences: what it searches, what it returns and in what order, then the next step. No filler, and the search scope is front-loaded.

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?

With no output schema, the description carries the return-value burden and does so: it names the result cap, ordering, distance semantics and two decision-relevant flags, plus the follow-up call. That is enough for an agent to call it correctly and chain it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with examples, default and maximum for rayon_km, so the baseline is 3. The description adds meaning beyond the schema by explaining where the latitude/longitude values come from (patient position or geocoded address), though it says nothing extra about the radius parameter.

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 verb and resource: searches masseurs-kinésithérapeutes registered on MonRdvKiné around GPS coordinates. The geographic scoping implicitly separates it from the sibling rechercher_kines (a name-based search), but the description never names that sibling explicitly, so differentiation is inferred rather than stated.

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?

Gives clear usage context: coordinates come from the patient's position or a geocoded address, and the tool is a first step in a workflow, followed by disponibilites_nouveau_patient with the returned PhysicianId. It stops short of stating when NOT to use it (e.g. searching by practitioner name), leaving that to the agent.

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