Skip to main content
Glama

Find Draw Sites

find-draw-sites
Read-onlyIdempotent

Find Quest Diagnostics patient service centers (blood-draw sites) near a 5-digit US ZIP code where a JustLabs order can be collected: site code, address, distance, hours, walk-ins and a booking link, optionally with the next open appointment times. Send only a ZIP code — never a street address, name or contact details. The response names the states where JustLabs does not accept orders.

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": {
      "zip": "<zip>"
    },
    "name": "find-draw-sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
limitNo
radiusMilesNo
includeSlotsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, open-world, non-destructive lookup, so the description is not burdened with safety basics. It still adds real context the annotations cannot convey: the PII restriction on inputs and the fact that the response names states where JustLabs does not accept orders, which tells the agent to expect a possible coverage-gap signal in the output. It does not mention rate limits, result ordering, or what happens when the radius yields nothing.

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?

Structure is sound: the purpose and search radius come first, the returned fields follow, then the input-safety rule and the coverage caveat. Three sentences, no filler. The middle field-list is long but each item is informative, so nothing feels padded.

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 compensates by enumerating the return fields and flagging the unsupported-states message. For a four-parameter read tool with full annotation coverage, that is nearly sufficient; the omission of `limit` and `radiusMiles` behavior is the main remaining hole.

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?

Schema description coverage is 0%, so the description carries the burden. It well explains `zip` (must be a 5-digit ZIP, never a street address) and indirectly reveals `includeSlots` ('optionally with the next open appointment times'), but `limit` and `radiusMiles` are never mentioned or given defaults/semantics. Two of four parameters remain undocumented in both schema and description, which is a real gap for a 0%-coverage schema.

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 resource (Quest Diagnostics patient service centers / blood-draw sites) and a specific scope (near a 5-digit US ZIP, where a JustLabs order can be collected), then enumerates what comes back: site code, address, distance, hours, walk-ins, booking link. No sibling tool in the list does anything comparable, so an agent can route here without ambiguity.

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 gives clear conditions for use: a 5-digit US ZIP input, a JustLabs order that needs collection, and the explicit exclusion 'Send only a ZIP code — never a street address, name or contact details.' It also signals an optional mode ('next open appointment times'). What it lacks is any statement of when NOT to use it or which sibling to prefer for adjacent needs such as pricing or test details.

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