Skip to main content
Glama

BRAINIAC License Renew

Read verified licence renewal requirements

license_requirements

Return source-linked rules only for supported Texas electrician and UK SIA licence types; unsupported jurisdictions remain explicitly unsupported. Price $0.01 USDC. POST /api/v1/license/requirements. Unpaid calls return 402 and do not run.

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": {
      "jurisdiction": "<jurisdiction>",
      "licenseType": "<licenseType>"
    },
    "name": "license_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseTypeYes
jurisdictionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the $0.01 USDC price, the POST transport, and the 402 failure mode with the guarantee that unpaid calls do not execute. It stops short of describing the return payload or rate limits, and a POST-based read operation could confuse an agent about side effects.

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 terse clauses with the capability and scope front-loaded, then pricing, transport, and failure semantics in descending order of importance. Nothing is padded and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no annotations and no output schema, the description covers scope, cost, and payment failure but leaves the return shape undefined — 'source-linked rules' is not concretely described, and the agent cannot tell what fields to expect or whether results are paginated.

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 0%, so the description must compensate, and it meaningfully narrows both free-string parameters: jurisdiction to Texas and the UK, licenseType to electrician and SIA licence types. It does not give the literal accepted values, so an agent still has to guess the exact spelling for these unenumerated fields.

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 definition uses a specific verb ('Return') and resource ('source-linked rules'), and hard-bounds the scope to Texas electrician and UK SIA licence types. That scoping alone separates it from license_renewal-plan and license_deadline-watch, though it never names those siblings explicitly.

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?

It tells the agent when this tool applies ('only for supported Texas electrician and UK SIA licence types') and what happens outside that scope ('explicitly unsupported'). However, it gives no guidance on which sibling to use for plans or deadlines, or what to do when a jurisdiction is unsupported beyond the refusal.

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