Skip to main content
Glama

compare_rules

Compare a specific rule field across 2–10 states. Only states with verified: true carry a rule. Treat null as "not verified", not "no rule". Input formats: states as two-letter codes (FL, GA, TX); field is one of licensing, licenseTypes, deductibleWaiver, depositRule, permit, insurance, unlicensedPenalty, rightToCancel, aob.

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": {
      "states": "<states>",
      "field": "<field>"
    },
    "name": "compare_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
statesYesTwo-letter state codes, e.g. ["FL", "GA"]

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?

With no annotations, the description carries the behavioral burden and does disclose a material data-semantics rule that the schema cannot express: only verified:true states carry a rule, and null must be read as 'not verified' rather than 'no rule'. It does not cover return shape, auth, or rate limits, but the disclosed caveat is the one most likely to cause misinterpretation.

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?

Three tight sentences with the core action front-loaded, followed by the interpretation caveat and then input formats. No filler, and the ordering matches the order an agent needs the 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 read-only comparison with no output schema and no annotations, it supplies the essential input formats and the critical null-vs-not-verified semantics. It stops short of describing what the comparison result looks like or how missing states appear in the response.

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 description coverage is only 50% (the 'field' enum has no schema description), and the description compensates by enumerating all nine valid field values and restating the two-letter code format for states. The format notes partly duplicate the schema, but the field-value list genuinely fills the coverage gap.

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 (compare), a specific resource (a rule field), and an explicit scope (2–10 states). The multi-state comparison framing inherently separates it from single-state siblings like state_rules, but no sibling is named, so it falls short of the top tier.

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 implied by the scope statement (cross-state field comparison), and the verified/null caveat guides result interpretation. However, it never states when to prefer this over state_rules or changes_since, nor does it set exclusions, leaving alternative selection to inference.

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