Skip to main content
Glama

BRAINIAC License Renew

Build a sourced renewal plan

license_renewal-plan

Calculate a renewal checklist and PDF from verified rules and caller-supplied expiry/CE data. Unsupported combinations remain unsupported. Price $0.05 USDC. POST /api/v1/license/renewal-plan. 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_renewal-plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
expiresOnNo
licenseTypeYes
jurisdictionYes
completedCeHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does well: it discloses the price ($0.05 USDC), the transport (POST /api/v1/license/renewal-plan), and the failure mode that unpaid calls return 402 and do not execute. It also warns that unsupported combinations are not handled, which sets a real behavioral expectation. It stops short of describing the success response shape or how the PDF is delivered.

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?

Five short sentences with the core purpose front-loaded, followed by the coverage caveat and then the commercial/transport facts. The endpoint line is of marginal value to an agent already invoking the tool, but nothing is padded or repetitive.

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 four-parameter tool with no output schema and no annotations, the description covers cost, endpoint, and payment failure but leaves the return contract vague ('checklist and PDF' with no format or delivery detail) and does not say whether unsupported combinations produce an error or a partial result.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate for four undocumented parameters. It implicitly references expiresOn and completedCeHours via 'expiry/CE data' and hints at jurisdiction/licenseType through 'unsupported combinations,' but adds no format, vocabulary, or accepted-value guidance beyond what the raw schema types convey.

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 and concrete artifacts: 'Calculate a renewal checklist and PDF from verified rules and caller-supplied expiry/CE data.' An agent can tell it produces a renewal plan rather than raw requirements, but the description never names or contrasts with the siblings license_requirements and license_deadline-watch, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no named alternative. 'Unsupported combinations remain unsupported' signals a coverage boundary but does not tell the agent what to do in that case or when to prefer license_requirements instead. Usage must be inferred from the purpose sentence.

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