patient-services

get_aftercare_information

Read-only

Returns the clinic's remote follow-up schedule and the process for handling a suspected problem after a patient has returned home.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`evidence`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 13, 2026

addedOutput schema / properties / data / properties / discharge_pack

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / emergency_limitation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / local_dentist_liaison
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / data / required

Previous value: -[
-  "aftercare_guide",
-  "canonical_url",
-  "corrective_trip_terms",
-  "entity_id",
-  "evidence",
-  "follow_up_schedule",
-  "in_clinic_follow_up",
-  "remote_problem_process",
-  "summary"
-]New value: +[
+  "aftercare_guide",
+  "canonical_url",
+  "corrective_trip_terms",
+  "discharge_pack",
+  "emergency_limitation",
+  "entity_id",
+  "evidence",
+  "follow_up_schedule",
+  "in_clinic_follow_up",
+  "local_dentist_liaison",
+  "remote_problem_process",
+  "summary"
+]

Changed1 schema field changedAug 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "properties": {
+        "aftercare_guide": {
+          "type": "string"
+        },
+        "canonical_url": {
+          "type": "string"
+        },
+        "corrective_trip_terms": {
+          "type": "string"
+        },
+        "entity_id": {
+          "type": "string"
+        },
+        "evidence": {
+          "items": {
+            "properties": {
+              "checked_at": {
+                "type": "string"
+              },
+              "source": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "checked_at",
+              "source",
+              "url"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "follow_up_schedule": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "in_clinic_follow_up": {
+          "type": "string"
+        },
+        "remote_problem_process": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "aftercare_guide",
+        "canonical_url",
+        "corrective_trip_terms",
+        "entity_id",
+        "evidence",
+        "follow_up_schedule",
+        "in_clinic_follow_up",
+        "remote_problem_process",
+        "summary"
+      ],
+      "type": "object"
+    },
+    "evidence": {
+      "items": {
+        "properties": {
+          "checked_at": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "source",
+          "url",
+          "checked_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "properties": {
+        "canonical_url": {
+          "type": "string"
+        },
+        "entity_id": {
+          "type": "string"
+        },
+        "last_updated": {
+          "type": "string"
+        },
+        "source_status": {
+          "enum": [
+            "verified",
+            "published"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "entity_id",
+        "canonical_url",
+        "source_status"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "meta",
+    "evidence"
+  ],
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety. The description adds no additional behavioral details beyond the content returned, but it doesn't contradict annotations. This is adequate given the annotation coverage.

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?

The description is a single sentence that front-loads the verb 'Returns' and clearly specifies the content. Every word earns its place with no redundancy or fluff.

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?

This is a simple read-only tool with no parameters, full annotations, and an output schema. The description accurately covers the tool's purpose without missing critical information, making it complete for an agent to invoke correctly.

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?

The tool has zero parameters, so the description doesn't need to explain parameter formats. Per the rubric, a baseline of 4 is appropriate when no parameters exist.

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 clearly states the tool returns two specific things: the clinic's remote follow-up schedule and the process for handling a suspected problem after a patient returns home. This distinguishes it from siblings like get_visit_information and get_clinic_profile by specifying the aftercare context.

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?

The description implies usage for post-discharge scenarios, which is clear from the phrase 'after a patient has returned home.' It does not explicitly name alternatives or exclusions, but the context is specific enough for an agent to determine when to use this tool over others.

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

All patient-services 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?