Skip to main content
Glama
Sign In
Connects to Epic MyChart patient portals to log in, list test results, and download them as PDFs so an AI assistant can help understand your own lab work.

Connects to Epic MyChart patient portals to log in, list test results, and download them as PDFs so an AI assistant can help understand your own lab work.

by kriskraw80
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get MyChart Test Result Details

mychart_get_test_result
Read-onlyIdempotent

Get a specific test result's full readable content—component values, reference ranges, flags, and comments—so you can understand your lab results.

Instructions

Open one test result and return its full readable content — component values, reference ranges, flags, and provider comments — as text. Requires a logged-in session.

Args:

  • result_id (string): An id from mychart_list_test_results (e.g. "r3"), or a full result-detail URL.

Returns: { id, name, date, url, text, truncated }. If truncated is true, use mychart_download_test_result for the complete PDF.

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": {
      "result_id": "<result_id>"
    },
    "name": "mychart_get_test_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
result_idYesResult id from mychart_list_test_results (e.g. "r3") or a full result URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent behavior, but the description adds valuable context: the need for a logged-in session, the return format including a truncated flag, and the fallback to download for full PDFs. This goes beyond the annotations and helps the agent understand operational requirements and limitations.

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 well-organized with separate sections for the main purpose, arguments, and return value. Every sentence provides essential information without fluff, making it easy to parse and understand.

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?

For a tool with a single parameter and no output schema, the description fully covers what the agent needs: the input source, session requirement, return fields, and truncation handling. It even references the relevant sibling tool for complete PDFs, making it self-contained.

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?

The input schema already provides a full description of result_id, and the description's Args section repeats the same information. Since schema coverage is 100%, the description adds no new meaning to the parameter beyond what is already structured.

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 opens one test result and returns full readable content including component values, reference ranges, flags, and provider comments. It distinguishes from siblings like mychart_list_test_results and mychart_download_test_result by focusing on a single result's detailed readable text.

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 mentions the prerequisite of a logged-in session and points to mychart_download_test_result as an alternative when truncated is true. It also references mychart_list_test_results as the source for result IDs. However, it does not explicitly state when to use this tool versus listing or downloading in all cases, though the context is clear.

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

Deploy Server

Other Tools