Skip to main content
Glama

Hospital procedure volumes in France

hospital_procedure_volumes
Read-onlyIdempotent

France only. Which French hospitals and private clinics perform a procedure most, from Open CCAM (ATIH): number of acts per hospital site per year, 2021-2025, public and private. Counts hospital stays and day cases only (PMSI MCO); procedures done in a doctor's office or a hospital outpatient clinic are not counted, and a site with fewer than 11 stays for an act is not listed. procedure = English or French text ('cataract', 'knee replacement', 'prothèse genou', 'coloscopie', 'ablation fibrillation auriculaire') or CCAM codes; the reply lists the CCAM acts it added up, so check they fit the need (add-on codes and pathology are left out of text matches). For 'aneurysm' or 'stent' say where (brain, aorta, heart, carotid). place = city, postcode, Paris/Lyon/Marseille arrondissement, département number or a hospital FINESS number; without place it ranks all of France. Hospital-level only: it does not say which surgeon operates. Then use search_doctors with hospital_finess (salaried hospital doctors) or with the hospital's postcode and the specialty (self-employed surgeons at private clinics). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hospital_procedure_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoDefault latest (2025).
codesNoExact CCAM codes to add up (use instead of procedure to narrow).
limitNoDefault 10.
placeNoCity, postcode, arrondissement ('Paris 15'), département number (2A, 2B, 971-976), or hospital FINESS number.
offsetNoFor paging (at most 100).
procedureNoProcedure in English or French, or CCAM codes (e.g. 'BFGA427'; an 8th phase digit is dropped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior: it counts PMSI MCO stays and day cases only, excludes office/outpatient-clinic procedures, suppresses sites with fewer than 11 stays, and reports which CCAM acts were summed. This is exactly the kind of operational detail annotations cannot convey.

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 hard constraint 'France only' and dense with useful detail, so most sentences earn their place. However it is a long, run-on paragraph mixing counting rules, input syntax, and tool routing, which slightly hurts scanability.

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 notes the reply lists the CCAM acts that were summed and that counts reflect hospital stays/day cases. Combined with schema-documented paging (limit/offset/year), an agent has everything needed to call and interpret 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%, so baseline is 3, but the description adds real meaning: procedure accepts English or French free text or CCAM codes, examples are given, an 8th phase digit is dropped, add-on codes and pathology are excluded from text matches, and place accepts city/postcode/arrondissement/département/FINESS. It goes beyond the schema's terse descriptions.

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: ranking French hospitals/clinics by how often they perform a given procedure, from Open CCAM (ATIH), per site per year. It scopes the source, years, and public/private coverage, making it clearly distinct from siblings like search_doctors and list_procedures.

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?

Explicitly bounds use ('France only') and routes the agent onward: 'Then use search_doctors with hospital_finess ... or with the hospital's postcode and the specialty.' It also clarifies that the tool is hospital-level only and does not identify surgeons, so the agent knows exactly when to stop and switch tools.

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