Skip to main content
Glama

mediora-mcp

by io.github.SLAtech-IL

mediora__get_patient_history

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.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses pagination (default 10 per page), authentication requirements (patient-scope JWT), and that the tool proxies an external API with token forwarding. This is comprehensive 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.

Conciseness5/5

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

Two sentences, no filler. The most critical info (purpose, authentication, pagination) is front-loaded. Every sentence is earned.

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?

Given no output schema, the description lists the returned fields. It covers authentication, pagination, proxying, and required token type. This is fully adequate for a tool with 3 parameters and no output schema.

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?

Schema coverage is 100%, so the description adds value beyond schema by specifying that bearer_token must be a patient-scope JWT and providing pagination context. It could further explain the page parameter's 1-based nature (already in schema) or the token's source.

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 uses a specific verb ('Return') and resource ('patient's past medical-test rows'), lists the returned fields, and distinguishes from sibling tools like mediora__get_test_details by implying this is a list/history endpoint.

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 states the bearer token must be a Mediora patient-scope JWT and references mediora__whoami for obtaining it. It mentions pagination defaults. However, it does not explicitly guide when to use this tool vs alternatives like mediora__get_test_details.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: catalog list/explain tools are divided by entity type (condition, marker, panel, symptom), patient data tools separate history, details, and trend analysis, and analyze_lab_pdf/whoami have unique roles. No two tools could reasonably be confused.

Naming Consistency4/5

The set overwhelmingly follows a verb_noun pattern (list_*, explain_*, get_*, analyze_lab_pdf, lookup_marker, whoami). The only deviation is 'longitudinal_trend', which is a noun phrase rather than an action verb; still clearly readable.

Tool Count5/5

At 14 tools, the set is well-scoped for a domain that spans catalog browsing, patient data retrieval, and lab report analysis. Each tool serves a distinct purpose and none feel redundant.

Completeness5/5

The lifecycle is complete: authenticate (whoami), ingest a lab PDF (analyze_lab_pdf), retrieve patient history (get_patient_history), drill into details (get_test_details), and analyze longitudinal patterns (longitudinal_trend). The catalog is fully browsable with list_* and explain_* tools, and lookup_marker bridges aliases. No obvious missing operations.

Resources