Skip to main content
Glama

Non-resident pharmacy licensing in a state

nonresident_licensing
Read-onlyIdempotent

Returns what a state's pharmacy board publishes about licensing a pharmacy located outside that state that ships into it, quoted word for word with source and date, grouped by topic. Says which states Provkeep reads for this when the state asked about is not one of them. 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>"
    },
    "name": "nonresident_licensing"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesA US state, as its two letter code (OH) or its name (Ohio).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description still adds real value: results are quoted verbatim with source and date and grouped by topic, unsupported states return the list Provkeep actually covers, and the call is metered ("counts as one lookup"). It does not address freshness or how current the quoted material is.

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 compact sentences with the resource description front-loaded, followed by fallback behavior and cost. The phrasing "Says which states Provkeep reads for this" is slightly oblique but still brief and purposeful.

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 carries the burden of describing the return shape and does so (verbatim quotes, source, date, topical grouping). Fallback for uncovered states is covered; only freshness/staleness of the published material is left unaddressed, which is minor for a read-only lookup.

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?

Only one parameter exists and the schema fully documents it (two-letter code or state name). The description adds nothing about the state parameter beyond what the schema already says, so the baseline of 3 applies.

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?

"Returns what a state's pharmacy board publishes about licensing a pharmacy located outside that state that ships into it" names a specific verb, a specific resource (non-resident licensing publications), and the exact scope of what is and is not included. It is clearly distinct from rules-oriented siblings such as lookup_rules or order tools.

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?

Usage is only implied: the description establishes that this is a per-state lookup costing one unit, which nudges an agent to use it for a single state query. It never states when to prefer it over a sibling like lookup_rules, nor any exclusions or prerequisites.

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