Skip to main content
Glama

StatuteWire

screen_roster

Adds practitioners to the account's roster for monthly monitoring (up to 500 per call). It does NOT return screening results: results arrive with the next monitoring run and are read with get_receipt (roster_id + period). Each entry needs NPI + first name + last name. Quota or prepaid debit is applied as POST /api/v1/rosters/bulk applies it (one unit per newly enrolled license; duplicates and failures are free; prepaid live keys also need the enterprise deposit floor). Sandbox keys enrol sample data only; nothing is screened for real. Not covered: instant results, people without an NPI. 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": {
      "entries": "<entries>"
    },
    "name": "screen_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes well beyond them by disclosing billing mechanics (one unit per newly enrolled license, duplicates and failures free, prepaid enterprise deposit floor), sandbox sample-data limits, and the auth error behavior. Minor gap: it doesn't say whether a partially failed batch can be retried safely or how duplicates are detected.

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?

Front-loaded with the core action and the negative scope, and nearly every sentence carries operational information. The quota/prepaid sentence is dense and packs several billing rules into one clause chain, which costs some readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no output schema, the description covers what happens to the submitted data, when results appear and how to fetch them, cost implications, sandbox limits, unsupported cases, and auth failure behavior. Nothing an agent needs in order to call this correctly is missing.

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 low, and the description only clarifies the three required entry fields ('NPI + first name + last name') plus the 500 cap, both of which are largely already visible in the schema. The optional fields (state, profession enum, license_number) carry no added meaning in the description, so it only partially compensates for the coverage 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?

States a specific verb and resource ('Adds practitioners to the account's roster for monthly monitoring'), gives a batch size limit, and explicitly separates itself from result retrieval ('It does NOT return screening results... read with get_receipt'). An agent can distinguish this from screen_practitioner and get_receipt without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative path for results (get_receipt with roster_id + period), lists exclusions ('instant results, people without an NPI'), and points to how_to_get_access when unauthenticated. Sandbox behavior is also flagged, so the agent knows when this tool will not produce real screening.

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