Skip to main content
Glama
Sign In

mediora-mcp

by io.github.SLAtech-IL
OverviewDiscussionsAdmin

Test details

mediora__get_test_details
Read-onlyIdempotent

Return the persisted markers + AI analysis (Summary, KeyFindings, Recommendations, DetailedExplanation) for a specific medical-test the authenticated patient owns. Use after mediora__get_patient_history surfaces a test id the user wants to discuss. Bearer token must be a Mediora patient-scope JWT. Proxies https://api.mediora.ai/api/medical-tests/{id} 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>",
      "test_id": "<test_id>"
    },
    "name": "mediora__get_test_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYesNumeric medical-test id (returned by mediora__get_patient_history as `id`).
bearer_tokenYesMediora.AI patient JWT (see mediora__whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses ownership scoping (the patient must own the test), the token scope required, and the fact that the call proxies https://api.mediora.ai/api/medical-tests/{id} with the user's bearer token forwarded. That tells the agent where data comes from and why auth failures are likely, which is exactly the context annotations cannot carry.

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 sentences, front-loaded with the payload and its four fields, then the sequencing hint, then the auth/proxy mechanics. No filler and no restatement of the title.

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?

No output schema exists, and the description compensates by naming the returned sections (Summary, KeyFindings, Recommendations, DetailedExplanation). Combined with the auth mechanics and id provenance, an agent has everything needed to call it correctly and interpret the result.

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 baseline is 3; the description still adds the provenance of test_id (an `id` from patient history) and sharpens the token requirement to a patient-scope JWT forwarded as Authorization: Bearer. That goes slightly beyond the schema's generic "Mediora.AI patient JWT" wording.

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?

Specific verb (Return) plus a precisely enumerated resource (persisted markers + AI analysis with the four named sections) scoped to a medical-test the authenticated patient owns. It is clearly distinguishable from mediora__get_patient_history, which surfaces the ids rather than the detail payload.

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

Usage Guidelines5/5

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

"Use after mediora__get_patient_history surfaces a test id the user wants to discuss" gives an explicit trigger condition and names the sibling that produces the required input. It also states the auth prerequisite (patient-scope JWT), so the agent knows both when and how to be eligible to call it.

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