Skip to main content
Glama

Pre-check an order's products against a state

precheck_order
Read-onlyIdempotent

For an order before a prescriber or pharmacist reviews it: for each product, returns what the destination state's own sources and the federal agencies published, quoted with source and date, and marks any sentence that is limited to a purpose or a type of consult. Records nothing and returns no pass or fail. Takes only product names, the two letter state, and optional purpose and consult type codes; send no patient or prescriber details. Counts as one lookup.

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": {
      "state": "<state>",
      "products": "<products>"
    },
    "name": "precheck_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesA US state, as its two letter code (OH) or its name (Ohio).
purposeNoOptional. Why it is prescribed, as a code.
productsYesThe products on the order, by name.
consult_typeNoOptional. How the patient was seen, as a code.

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?

Beyond the annotations (readOnlyHint, idempotent, closed-world), the description discloses that it records nothing, that results are quoted with source and date, that sentences limited to a purpose or consult type get flagged, and that a call 'counts as one lookup' — a cost/quota signal an agent cannot get from structured fields. It does not cover failure modes (unknown product, invalid state), which keeps it from a 5.

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?

Purpose and timing are front-loaded, then the return shape, then the input restrictions. Densest packing is one long colon-led sentence, and the parameter recital partly duplicates the schema, but every clause carries information and nothing is padding.

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, so the description must characterize returns — it does so qualitatively (per-product quotes with source and date, purpose-limited sentences marked, no pass/fail). That is enough for an agent to call it correctly, though the concrete response structure remains implicit.

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% and the enums are self-describing, so the baseline is 3; the description adds real meaning by restricting the input surface to product names, the two-letter state, and optional purpose/consult codes, and explicitly forbidding patient or prescriber data — a constraint that matters even with additionalProperties:false.

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?

A concrete verb and resource: it pre-checks each product on an order against the destination state's own sources plus federal agencies, returning quoted material with source and date. That is far more specific than the title alone and clearly separates it from write-oriented siblings like record_order. It stops short of naming a contrasting lookup (e.g. lookup_rules), so the 5 is not earned.

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?

The timing condition is explicit: 'For an order before a prescriber or pharmacist reviews it.' It also sets a hard boundary ('send no patient or prescriber details') and warns the caller not to expect a verdict ('returns no pass or fail'), which steers against misuse as an approval gate. No alternatives are named, so it is context-clear but not exhaustive.

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