Taiwan Laboratory MCP

Overview Schema Source Related Servers Discussions Admin

get_testing_location

Find where to send a CDC specimen for a disease, including testing duration and the receiving unit's phone, fax, and address.

Instructions

Where a CDC specimen is sent and how long the test takes, with the receiving unit's phone, fax and address. decision_support_only=true; verify_current_official_source=true; not_validated_for_hospital_deployment=true; not_pre_submission_storage=true. 不得輸入病人資料。手冊第 7 章：一種疾病常有好幾列（不同檢驗方法各一列），檢驗期限與 7.7 的檢驗期間是不同欄位，不可互相代用。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`disease`	Yes

Output Schema

TableJSON Schema

Name	Required	Default
`items`	Yes
`limit`	Yes
`notes`	Yes
`query`	Yes
`offset`	Yes
`safety`	Yes
`warnings`	Yes
`data_mode`	Yes
`operation`	Yes
`truncated`	Yes
`provenance`	Yes
`sample_only`	Yes
`availability`	Yes
`result_status`	Yes
`source_status`	Yes
`total_matches`	Yes
`returned_count`	Yes
`coverage_detail`	Yes
`coverage_status`	Yes
`evaluated_as_of`	Yes
`contract_version`	No	public-contract-v1
`evaluated_timezone`	Yes
`snapshot_traceable`	Yes
`replacement_operation`	Yes
`availability_reason_code`	Yes
`historical_truth_supported`	Yes
`currently_reproducible_from_upstream`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.3Sep 17, 2026

addedOutput schema / $defs / CDCManualClauseRecord

Added value: +{
+  "additionalProperties": false,
+  "description": "One numbered clause, figure caption or appendix form of the manual, as printed.",
+  "properties": {
+    "block_kind": {
+      "enum": [
+        "clause",
+        "figure",
+        "appendix"
+      ],
+      "title": "Block Kind",
+      "type": "string"
+    },
+    "chapter": {
+      "title": "Chapter",
+      "type": "string"
+    },
+    "clause_number": {
+      "title": "Clause Number",
+      "type": "string"
+    },
+    "record_type": {
+      "const": "cdc_manual_clause",
+      "default": "cdc_manual_clause",
+      "title": "Record Type",
+      "type": "string"
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "block_kind",
+    "clause_number",
+    "chapter",
+    "text"
+  ],
+  "title": "CDCManualClauseRecord",
+  "type": "object"
+}

addedOutput schema / $defs / ItemEnvelope / properties / record / discriminator / mapping / cdc_manual_clause
```
Added value: +"#/$defs/CDCManualClauseRecord"
```

changedOutput schema / $defs / ItemEnvelope / properties / record / oneOf

Previous value: -[
-  {
-    "$ref": "#/$defs/NHIRecord"
-  },
-  {
-    "$ref": "#/$defs/NHISearchRecord"
-  },
-  {
-    "$ref": "#/$defs/CDCSpecimenRecord"
-  },
-  {
-    "$ref": "#/$defs/CDCTestingLocationRecord"
-  },
-  {
-    "$ref": "#/$defs/CDCLabRecord"
-  },
-  {
-    "$ref": "#/$defs/TFDARecord"
-  },
-  {
-    "$ref": "#/$defs/TFDASearchRecord"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/NHIRecord"
+  },
+  {
+    "$ref": "#/$defs/NHISearchRecord"
+  },
+  {
+    "$ref": "#/$defs/CDCSpecimenRecord"
+  },
+  {
+    "$ref": "#/$defs/CDCTestingLocationRecord"
+  },
+  {
+    "$ref": "#/$defs/CDCManualClauseRecord"
+  },
+  {
+    "$ref": "#/$defs/CDCLabRecord"
+  },
+  {
+    "$ref": "#/$defs/TFDARecord"
+  },
+  {
+    "$ref": "#/$defs/TFDASearchRecord"
+  }
+]

changedOutput schema / properties / operation / enum

Previous value: -[
-  "get_data_status",
-  "search_disease",
-  "get_specimen_requirement",
-  "get_collection_method",
-  "get_container",
-  "get_transport_requirement",
-  "get_submission_rule",
-  "get_testing_location",
-  "find_authorized_lab",
-  "get_lab_scope",
-  "search_payment_items",
-  "search_lab_code",
-  "get_points",
-  "get_payment_rule",
-  "search_reviewed_ivd",
-  "search_ivd_candidates",
-  "search_ivd",
-  "get_license",
-  "find_manufacturer",
-  "list_matching_license_records",
-  "compare_products",
-  "standards_status",
-  "eqa_status"
-]New value: +[
+  "get_data_status",
+  "search_disease",
+  "get_specimen_requirement",
+  "get_collection_method",
+  "get_container",
+  "get_transport_requirement",
+  "get_submission_rule",
+  "get_testing_location",
+  "search_manual_procedure",
+  "find_authorized_lab",
+  "get_lab_scope",
+  "search_payment_items",
+  "search_lab_code",
+  "get_points",
+  "get_payment_rule",
+  "search_reviewed_ivd",
+  "search_ivd_candidates",
+  "search_ivd",
+  "get_license",
+  "find_manufacturer",
+  "list_matching_license_records",
+  "compare_products",
+  "standards_status",
+  "eqa_status"
+]

changedOutput schema / properties / replacement_operation / anyOf

Previous value: -[
-  {
-    "enum": [
-      "get_data_status",
-      "search_disease",
-      "get_specimen_requirement",
-      "get_collection_method",
-      "get_container",
-      "get_transport_requirement",
-      "get_submission_rule",
-      "get_testing_location",
-      "find_authorized_lab",
-      "get_lab_scope",
-      "search_payment_items",
-      "search_lab_code",
-      "get_points",
-      "get_payment_rule",
-      "search_reviewed_ivd",
-      "search_ivd_candidates",
-      "search_ivd",
-      "get_license",
-      "find_manufacturer",
-      "list_matching_license_records",
-      "compare_products",
-      "standards_status",
-      "eqa_status"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "get_data_status",
+      "search_disease",
+      "get_specimen_requirement",
+      "get_collection_method",
+      "get_container",
+      "get_transport_requirement",
+      "get_submission_rule",
+      "get_testing_location",
+      "search_manual_procedure",
+      "find_authorized_lab",
+      "get_lab_scope",
+      "search_payment_items",
+      "search_lab_code",
+      "get_points",
+      "get_payment_rule",
+      "search_reviewed_ivd",
+      "search_ivd_candidates",
+      "search_ivd",
+      "get_license",
+      "find_manufacturer",
+      "list_matching_license_records",
+      "compare_products",
+      "standards_status",
+      "eqa_status"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Addedv0.1.2Sep 16, 2026

TDQS

A3.6/5.0

Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden, and it delivers: trust-level flags, a PII input prohibition, and an interpretation caveat that one disease maps to multiple rows by testing method. However, the flags are terse and cryptically formatted — not_pre_submission_storage in particular reads as raw metadata rather than actionable behavioral context.

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

Conciseness2/5

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

The purpose sentence is front-loaded, but the remainder is a raw concatenation of key=value metadata flags and dense Chinese caveats fused into one block. The mixed-language, flag-dump structure hurts scannability and reads as unedited export content rather than a deliberate description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values are covered elsewhere, and the description does add output content plus interpretation caveats. The notable gaps are the disease parameter's value domain (unexplained at 0% coverage) and the cryptic flags like not_pre_submission_storage that need plain-language expansion to be actionable.

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?

With 0% schema description coverage, the description must compensate for the single disease parameter, and it does add one useful semantic: a disease often yields multiple rows, one per testing method, and the testing-deadline field is not interchangeable with the 7.7 testing-period field. But it never specifies the acceptable disease value format (name vs. code), valid values, or that search_disease exists to resolve the input — a real gap at 0% coverage.

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?

The opening sentence states exactly what the tool returns — where a CDC specimen is sent, test duration, and the receiving unit's phone/fax/address. This distinguishes it from siblings like get_transport_requirement (how to ship) and get_specimen_requirement (what to collect), though the contrast is never made explicit, so it stops short of a 5.

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 supplies explicit when-not-to-use constraints: decision_support_only=true, verify_current_official_source=true, not_validated_for_hospital_deployment=true, not_pre_submission_storage=true, and 'do not input patient data'. These are real exclusions for reliability and input safety, but no alternative sibling is named for the excluded scenarios, missing the full 5-level guidance.

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