Skip to main content
Glama

state_rules

Return what Roofer Registry has verified about a state's rules for roofing contractors: licensing, licenseTypes, deductibleWaiver, depositRule, permit, insurance, unlicensedPenalty, rightToCancel, aob — each { value, quote, citation, url } or null. Plus regulator, lookup URL, active-licensee count. If the state is not yet verified, the response says so — do not state a rule for that state from this source.

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": "state_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (each field as { value, quote, citation, url } or null), the null semantics for missing rules, and the unverified-state behavior plus the constraint not to state rules from this source. It does not cover auth requirements, rate limits, or that the call is purely read-only, leaving some behavioral gaps.

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 dense sentences that are front-loaded with the primary purpose and the returned field list; the long field enumeration is information-bearing rather than filler. The field catalog is somewhat list-heavy but every element earns its place by telling the agent what comes back.

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?

There is no output schema, and the description compensates by enumerating the returned fields and their value/quote/citation/url shape, including the unverified-state case. The main remaining gap is the input's expected state format, which is not addressed anywhere in the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is documented only as a bare string, yet the description says nothing about expected format (postal abbreviation vs full name) or case. Because the coverage is low, the description needed to compensate and does not, leaving a real risk of malformed invocation.

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 verb (Return) and a precisely scoped resource — what Roofer Registry has verified about a state's rules for roofing contractors — and enumerates every field returned (licensing, deductibleWaiver, permit, aob, etc.). The singular-state framing implicitly separates it from compare_rules, but no sibling is named explicitly, so it falls short of a 5.

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?

Provides one clear conditional rule: if a state is unverified the response says so, and the agent must not assert a rule from this source. That is useful guardrail guidance, but there is no routing advice versus check_license, compare_rules, or verify_live, so usage is only partially implied.

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