DoctoFam Medical Clinic

Look up consultation and service prices

list_procedures

Read-onlyIdempotent

Use this when someone asks what their medical practice charges for a consultation, check-up, vaccination or other service, or which procedure to book. Returns catalog service ids and names with price and last edit time, alphabetically, 50 per page by default. Not for a patient's medical history or the care they received.

Input Schema

Name	Required	Description
`limit`	No	Services per page, from 1 to 100; defaults to 50
`cursor`	No	The nextCursor of the previous page with the same filters; absent for the first page
`clinicId`	No	Only this practice (24 lowercase hexadecimal characters); every practice when absent

Output Schema

Name	Required	Description	Default
`nextCursor`	Yes	Cursor for the next page; null on the last page
`procedures`	Yes	Service catalog entries in name order, with the ids a booking takes. Patient-linked treatments, diagnoses and prescriptions are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

changedOutput schema / properties / procedures / description

Previous value: -"Service catalog entries in name order. Patient-linked treatments, diagnoses, prescriptions and record identifiers are never returned."New value: +"Service catalog entries in name order, with the ids a booking takes. Patient-linked treatments, diagnoses and prescriptions are never returned."

addedOutput schema / properties / procedures / items / properties / id

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9a-f]{24}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Id to book with, as book_appointment takes it"
+}

changedOutput schema / properties / procedures / items / required

Previous value: -[
-  "name",
-  "price",
-  "duration",
-  "lastEditTime"
-]New value: +[
+  "id",
+  "name",
+  "price",
+  "duration",
+  "lastEditTime"
+]

Changed7 schema fields changedSep 27, 2026

changedInput schema / properties / clinicId / description

Previous value: -"Filter by clinic id"New value: +"Only this practice (24 lowercase hexadecimal characters); every practice when absent"

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor from a prior result"New value: +"The nextCursor of the previous page with the same filters; absent for the first page"

addedInput schema / properties / limit / description

Added value: +"Services per page, from 1 to 100; defaults to 50"

addedOutput schema / properties / nextCursor / description

Added value: +"Cursor for the next page; null on the last page"

addedOutput schema / properties / procedures / description

Added value: +"Service catalog entries in name order. Patient-linked treatments, diagnoses, prescriptions and record identifiers are never returned."

addedOutput schema / properties / procedures / items / properties / duration / description
```
Added value: +"Configured duration, or null when none was recorded"
```
addedOutput schema / properties / procedures / items / properties / price / description
```
Added value: +"Price in the practice's currency"
```

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: results are alphabetical, paginated at 50 per page by default, and each row carries price and last edit time. Auth/clinic-scoping behavior is left to the schema's clinicId field rather than explained here.

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 compact sentences: trigger first, return shape and pagination second, exclusion last. Every sentence carries information and nothing is repeated from the title or schema.

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 three optional parameters, full schema coverage, and an output schema that documents the response, the description covers everything an agent needs: when to pick it, what comes back, ordering, page size, and what it is not for.

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%, so limit, cursor, and clinicId are already fully documented, which sets the baseline at 3. The description only reinforces the default page size and adds the alphabetical ordering, which isn't captured in the schema but is minor.

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?

The description states a specific verb and resource ('Look up ... what their medical practice charges for a consultation, check-up, vaccination or other service') and returns catalog service ids/names with price and last edit time. It is clearly distinguishable from siblings like list_inventory_items, list_providers, or get_clinic, which cover other catalog types.

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 an explicit trigger ('Use this when someone asks what their ... charges ... or which procedure to book') and an explicit exclusion ('Not for a patient's medical history or the care they received'). It stops short of naming the alternative sibling tool to use for history, but the when/when-not framing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DoctoFam Medical Clinic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?