Skip to main content
Glama

Get Guide

get-guide
Read-onlyIdempotent

Read a public JustLabs guide page as Markdown, e.g. /blood-test-preparation, /labs-for/hypothyroidism, /tests/tsh or /compare/everlywell. Pass a justlabs.health path starting with /, not a full URL. Account, checkout, results, admin and API paths are refused. Educational content; any range on the patient's own lab report applies.

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": {
      "path": "<path>"
    },
    "name": "get-guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds real value beyond that: the return format is Markdown, certain path classes are actively refused, and the closing sentence flags that content is educational and that the patient's own lab report range governs.

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?

Three sentences, front-loaded with the action and return format, then format rules, then scope exclusions. Dense and largely waste-free; the final 'Educational content' sentence is slightly cryptic in isolation but earns its place as a correctness caveat.

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?

For a one-parameter read tool with full annotations and no output schema, the definition covers action, input format, refusal behavior and return type. Remaining gaps (truncation limits, whether Markdown is paginated or size-bounded) are minor for a public page fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has zero schema description coverage (only minLength/maxLength), so the description carries the full burden and does so well: it specifies the expected form (a path beginning with '/'), forbids full URLs, lists three valid shapes and enumerates refused path prefixes. Only the 200-character cap goes unmentioned.

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?

States a specific verb and resource ('Read a public JustLabs guide page as Markdown') and grounds it with four concrete path examples spanning guide, lab, test and comparison pages. It does not explicitly distinguish itself from siblings like get-test-details or compare-prices, even though the sample paths overlap their territory, so an agent must infer the boundary.

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?

The description gives strong input constraints (must be a justlabs.health path starting with '/', not a full URL) and exclusions (account, checkout, results, admin, API paths refused), but never says when to choose this tool over the clearly related siblings such as get-test-details, compare-prices or lookup-reference-range. Usage is implied rather than routed.

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