Skip to main content
Glama

Look up a product's rules in a state

lookup_rules
Read-onlyIdempotent

Returns what a US state's own sources (its boards, register and laws) and the federal agencies (FDA, HHS, DEA) have published about a peptide or compounded drug, quoted word for word, each with its source link and the date Provkeep last read it. Says plainly when nothing is on record and how much of that state Provkeep reads. Leave out state to get the federal sources and the list of states whose own sources name the product. 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": {
      "product": "<product>"
    },
    "name": "lookup_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoA US state, as its two letter code (OH) or its name (Ohio).
productYesThe product's name, e.g. BPC-157, semaglutide, tirzepatide. list_products shows every name we match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the return content: verbatim quotations, source links, last-read dates, empty-result behavior, and state coverage limits. It also states the billing behavior as counting as one lookup, which is useful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every sentence contributes useful information about scope, return behavior, omission semantics, or lookup cost. It is dense but appropriately sized with no obvious filler.

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 two-parameter read-only lookup with no output schema, the description provides enough detail about return values, coverage limitations, no-result behavior, and optional parameter effects. An agent can use it correctly without additional behavioral documentation.

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%, so the schema already defines both parameters. The description adds meaningful behavior for omitting the optional state parameter, specifying that this returns federal sources and the list of states whose own sources name the product.

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?

The description states a specific lookup verb and a clear resource: what state and federal sources have published about a peptide or compounded drug. It explains the state-versus-federal scope, though it does not explicitly distinguish itself from sibling tools such as hhs_conditions.

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 usage context by explaining that omitting the state returns federal sources plus states whose sources name the product. It does not explicitly name when to prefer a sibling tool or when not to use this one.

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