Skip to main content
Glama

Recommend Tests

recommend-tests
Read-onlyIdempotent

Suggest JustLabs panels and tests for health goals (e.g. energy, heart health, fertility) and/or symptoms (e.g. fatigue, hair loss), each with a one-line reason, price, all-in price and link, plus the JustLabs guide pages the suggestion is based on. General education, not a diagnosis. Pass short goal or symptom words only — no names, contact details, dates of birth or lab results. Use get-pricing with the ids for the exact total.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend-tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsNo
symptomsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower — yet the description adds genuine context beyond them: the exact fields returned, a scope disclaimer that this is education not diagnosis, an explicit PII prohibition, and a caveat that listed prices are not the final total. These are behavioral constraints an agent could not recover from the annotations alone.

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?

The core purpose and examples come first, followed by the output field list, the safety disclaimer, the input constraint and the get-pricing handoff. It is dense but each clause carries information; the enumeration of four output fields in the first sentence is the only mildly heavy stretch.

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?

There is no output schema, and the description compensates by describing exactly what comes back, which is the critical missing piece for this tool. With only two optional parameters and full annotation coverage, almost nothing is left ambiguous; only the empty-input case and result-count behavior are unaddressed.

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 description coverage is 0%, so the description must carry the meaning, and it largely does: it explains that both inputs expect short goal or symptom words rather than names, contact details, dates of birth or lab results. It does not convey the practical limits enforced by the schema (60-char item cap, 10-item cap) or what happens if both arrays are omitted, leaving a small gap.

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 names a specific verb and resource — 'Suggest JustLabs panels and tests' — and scopes it to health goals (energy, heart health, fertility) and/or symptoms (fatigue, hair loss). It also enumerates the output shape (reason, price, all-in price, link, guide pages), so an agent can distinguish it from search-lab-tests or get-test-details without opening another schema.

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?

It sets clear context ('general education, not a diagnosis') and explicitly hands off price-total resolution to a named sibling: 'Use get-pricing with the ids for the exact total.' That is a real routing rule with an alternative named. It stops short of explicit when-not-to-use language against other siblings such as search-lab-tests, which keeps it below a 5.

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