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

Screenshot Current MyChart Page

mychart_screenshot
Read-only

Capture a full-page PNG of the current MyChart page to debug parsing failures. Use it to see what the portal actually rendered when automated result extraction comes up empty.

Instructions

Debug aid: capture a full-page PNG of whatever page the automation browser is currently on (or the MyChart home page if idle). Useful when list/detail scraping reports nothing recognizable — the screenshot shows what the portal actually rendered.

Args:

  • name (string, optional): Base filename for the PNG.

Returns: { path, url }. Screenshot is saved to ~/.mychart-mcp/downloads.

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": "mychart_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional base filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable behavioral details: the fallback behavior when idle, the file save location (~/.mychart-mcp/downloads), and the return format { path, url }. These go beyond what annotations convey and help the agent understand side effects and expectations.

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 concise and well-structured: it opens with the core purpose ('Debug aid: capture a full-page PNG'), then gives a practical use case, and finishes with compact Args and Returns sections. Every sentence earns its place without redundancy.

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 simple tool with one optional parameter and no output schema, the description is highly complete. It documents the return shape ({ path, url }), the save location, the fallback behavior when idle, and the intended debugging scenario. Nothing essential is missing.

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 only parameter 'name' is fully described in the schema as an optional base filename, and the description simply restates it in the Args section. Since schema coverage is 100%, the description adds no additional semantic meaning beyond the schema, so baseline 3 applies.

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's function: capture a full-page PNG of whatever page the automation browser is currently on, with a fallback to the MyChart home page. It identifies itself as a debug aid and specifies the resource (PNG) and scope, distinguishing it from sibling tools that focus on data retrieval or session management.

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 provides explicit context for when to use this tool: 'Useful when list/detail scraping reports nothing recognizable.' This gives a clear scenario. However, it does not explicitly mention when not to use it or alternative tools, so it lacks exclusions that would merit a 5.

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