Skip to main content
Glama
Sign In

mediora-mcp

by io.github.SLAtech-IL
OverviewDiscussionsAdmin

Check the patient token

mediora__whoami
Read-onlyIdempotent

Validate a Mediora.AI patient Bearer token and return the patient id + email it represents. Use this first to confirm the token before calling other auth-gated tools. The token is obtained by going through the standard Mediora.AI login at https://www.mediora.ai — the same JWT the browser stores in localStorage as 'auth_token'.

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__whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
bearer_tokenYesMediora.AI patient JWT. Get it by signing in at https://www.mediora.ai then copying localStorage.auth_token from DevTools, OR pass-through from a desktop client that stores Mediora credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered; the description adds that it returns patient id + email and where the JWT comes from (login at mediora.ai, localStorage 'auth_token'). It does not disclose what happens on an invalid or expired token (error vs empty result), which matters for a validation tool.

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, zero filler, with the purpose and the 'use first' directive front-loaded before the token-origin detail.

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?

With no output schema, the description correctly names the return values (patient id + email) and the token source. The one missing piece is failure behavior for an invalid/expired token, which an auth-gate tool should state.

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 goes slightly beyond by reiterating the token's origin and tying it to the browser's 'auth_token' key, reinforcing how to obtain the one required parameter.

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 ('Validate a Mediora.AI patient Bearer token') plus the return payload ('patient id + email'), which no sibling tool does. It is clearly distinguishable from the lookup/explain tools in the sibling list.

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?

Explicitly says 'Use this first to confirm the token before calling other auth-gated tools', giving both ordering and the condition that selects it. It also points to the login flow that produces the token, so an agent knows the prerequisite.

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