Skip to main content
Glama

BRAINIAC License Renew

Calculate licence reminder dates

license_deadline-watch

Return reminder dates from a caller-supplied expiry date. This is data only; BRAINIAC.software does not send notifications. Price $0.01 USDC. POST /api/v1/license/deadline-watch. 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": {
      "expiresOn": "<expiresOn>"
    },
    "name": "license_deadline-watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
expiresOnYes
remindDaysNo

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 supplied, the description does real work: it discloses that no notifications are sent (no side effects), states the price ($0.01 USDC), and documents the unpaid-call failure mode (HTTP 402, no execution). It stops short of describing the shape of the returned reminder data or any rate limits.

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 short sentences, front-loaded with the computation, then the side-effect disclaimer, then cost and endpoint. Every sentence adds a distinct fact an agent needs (behaviour, price, transport, failure mode).

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?

The tool is simple (2 params, no output schema), and the operational facts (cost, endpoint, 402) are present. But with no annotations and no output schema, the description should explain what the returned reminder dates look like and how remindDays changes them; that gap is what keeps this at minimum-viable.

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%, so the description must carry parameter meaning. It only covers the expiry input ('caller-supplied expiry date'); the remindDays parameter, its default [90, 30, 7], that values are day offsets, and its bounds (0–730, max 20 items) are never mentioned.

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?

Specific verb and resource: 'Return reminder dates from a caller-supplied expiry date', which is a computation, not a renewal plan or a requirements lookup. It is distinguishable in substance from license_renewal-plan and license_requirements, though it never names them.

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 only implied by the phrase 'from a caller-supplied expiry date', and the 'data only' clause implicitly tells the agent this is not a notification mechanism. There is no explicit when-to-use or when-not-to-use statement relative to the sibling licence tools.

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