Skip to main content
Glama

verify_live

Fetch the current license status directly from the state regulator (FL only) and compare it with our roster copy. Uses a 24-hour cache; the second call within 24h returns cached: true. Other states return { supported: false, lookupUrl }. Hard cap: 100 live fetches per UTC day.

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>",
      "license_number": "<license_number>"
    },
    "name": "verify_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
license_numberYese.g. CCC1325838

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/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 so thoroughly: it discloses the live fetch source, 24-hour cache behavior (cached: true on repeat calls), the hard cap of 100 live fetches per UTC day, and the return shape for unsupported states ({ supported: false, lookupUrl }). It also mentions comparison against the roster copy.

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?

Four compact clauses, each front-loaded with a distinct piece of critical information: purpose, cache behavior, unsupported-state response, and rate limit. No wasted words.

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 tool with no output schema and two parameters, the description supplies key operational details (cache, rate limit, unsupported-state return). It does not specify the exact return format or comparison details for supported states, which is a minor gap.

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 50% (state has no description, license_number has an example). The description adds meaningful constraint on the state parameter by stating 'FL only' and noting other states return a supported:false object, which clarifies expected input. It does not elaborate further on license_number formatting beyond the schema example.

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 verb+resource: fetch current license status directly from the state regulator and compare with roster copy. It also scopes to FL only and mentions caching, distinguishing it from a purely roster-based check. However, it does not explicitly name a sibling tool (e.g., check_license) as an alternative.

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 live-fetch scope and the 'FL only' constraint, and the description notes what happens for other states and the daily cap. It does not explicitly say when to use this tool versus siblings like check_license or search_licensees.

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