Skip to main content
Glama

StatuteWire

get_practitioner_history

Read-only

The append-only audit ledger of monitoring events for a practitioner on this account's roster (a practitioner screened or rostered by this key). Free (rate limited). Not covered: practitioners not on your roster (404). Entries made from sample data are not upgraded to live by this tool. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

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": {
      "npi": "<npi>"
    },
    "name": "get_practitioner_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYesThe 10-digit National Provider Identifier (NPI).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context on top: append-only immutability, free-but-rate-limited access, the 404 roster boundary, and that sample-data entries are not upgraded to live. The auth requirement and the error that redirects to how_to_get_access are also disclosed. Return payload shape is the only notable omission.

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 is front-loaded, then constraints, then auth, in a logical order with no filler. The nested parenthetical defining 'roster' and the run of short clipped sentences make it slightly dense but each clause carries distinct information.

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 single-parameter read tool with no output schema, the definition covers scope, cost/limits, failure mode, auth, and a data-freshness caveat. The main gap is that it does not hint at what an event entry contains, which matters since there is no output schema.

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 coverage is 100% for the single npi parameter, including the 10-digit pattern and its meaning, so the schema carries parameter semantics fully. The description adds nothing about the identifier beyond the roster constraint, which is the expected baseline.

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 resource with a precise noun phrase: an append-only audit ledger of monitoring events for a practitioner. That is far more informative than 'get history' and implicitly separates it from screening/verification siblings, but it never names an alternative tool or contrast explicitly.

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?

Gives useful scoping conditions: only practitioners on this account's roster, and a 404 for anyone else. It also flags 'Free (rate limited)' and the sample-vs-live caveat. What it lacks is any explicit routing guidance such as when to call this instead of screen_practitioner or verify_receipt.

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