Skip to main content
Glama
Sign In

mediora-mcp

by io.github.SLAtech-IL
OverviewDiscussionsAdmin

Patient test history

mediora__get_patient_history
Read-onlyIdempotent

Return the patient's past medical-test rows (id, test type, test date, risk level, summary, status, abnormal-marker count). Bearer token must be a Mediora patient-scope JWT. Paginated; default 10 per page. Proxies https://api.mediora.ai/api/medical-tests with the user's token forwarded as Authorization: Bearer.

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": {
      "bearer_token": "<bearer_token>"
    },
    "name": "mediora__get_patient_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
page_sizeNoItems per page. Defaults to 10, max 50.
bearer_tokenYesMediora.AI patient JWT (see mediora__whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds real value beyond them: the patient-scope token requirement, default page size of 10, and the fact that it proxies https://api.mediora.ai/api/medical-tests with the token forwarded.

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 tight sentences, front-loaded with the returned payload then auth, then pagination/upstream details; no filler.

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

Completeness4/5

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

No output schema exists, so listing the row fields is valuable and covers the return shape; auth and pagination are covered too. Only gaps are error/permission-failure behavior and empty-history behavior.

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 coverage is 100% and the schema already documents page, page_size (default 10, max 50) and the bearer_token; the description restates the page-size default and adds the token's required scope, but nothing beyond that. 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?

States a specific verb and resource ('Return the patient's past medical-test rows') and enumerates the returned fields, which distinguishes it from the singular mediora__get_test_details and from mediora__longitudinal_trend.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives context (patient-scope JWT required, pagination defaults) but does not say when to use this list versus mediora__get_test_details or mediora__longitudinal_trend, nor any exclusions.

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

All mediora-mcp toolsInspect
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