Skip to main content
Glama

Get Test Details

get-test-details

Get full details for a specific lab test or panel by its ID. Returns pricing, biomarkers (or included tests for a panel), preparation instructions, and turnaround time.

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": {
      "testId": "<testId>"
    },
    "name": "get-test-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
testIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does useful work by disclosing the return payload (pricing, biomarkers or included panel tests, preparation instructions, turnaround time) and by implying the ID may refer to either a test or a panel, but it says nothing about error behavior for an unknown ID, whether the call is read-only, or response size for large panels.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two compact sentences, front-loaded with the action and then the return contents, with no filler. Slight deduction because the return-value list is packed into a single sentence with no structure that would help an agent scan it.

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 and no annotations, the description is the only place return values could be documented and it does list them, including the test-versus-panel branch. What keeps it from full marks is the absence of any statement about ID provenance, failure modes, or the fact that pricing may be null/regional given the presence of separate pricing siblings.

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?

There is one parameter with 0% schema description coverage, so the description must compensate and only partially does. 'By its ID' establishes that testId is an identifier rather than a name, but the format (numeric, slug, opaque string), accepted prefixes, and whether panel IDs are valid in the same field are all left unspecified despite maxLength 80 being the only schema hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('Get full details for a specific lab test or panel by its ID') plus an enumeration of what comes back. It distinguishes itself from retrieval-by-search implicitly through 'by its ID', but never names a sibling such as search-lab-tests or get-test-panels to make the split unambiguous.

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?

Usage is only implied: the agent must infer that this is the follow-up call after obtaining an ID from a search tool. There is no explicit when-to-use, no when-not-to-use, and no statement about what to do if you only have a name rather than an ID.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources