Skip to main content
Glama

BRAINIAC Environmental, Carbon & Water Intelligence

Check environmental permit expiry

environmental-intelligence_permit-expiry-check

Check caller-supplied environmental permit expiry dates against asOf and a warning window. Compliance determinations are not made. Price $0.03 USDC. POST /api/v1/environmental-intelligence/permit-expiry-check. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "environmental-intelligence_permit-expiry-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
factorsNo
permitsNo
reportsNo
suppliersNo
activitiesNo
waterRecordsNo
waterAnomalyZNo
wasteManifestsNo
carbonIntensityNo
expiryWarningDaysNo
consistencyToleranceKgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose concrete traits: a $0.03 USDC charge, the POST endpoint, and that unpaid calls return 402 and do not execute. It does not describe the response shape (e.g., which permits are flagged expired vs. expiring), how the warning window is applied, or behavior on malformed dates.

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?

Four short, front-loaded sentences with no filler: the core action comes first, followed by scope boundary, price, endpoint, and payment failure behavior. Only the raw endpoint string is arguably low-value for an agent that already has the tool binding.

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

Completeness2/5

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

For a tool with 17 parameters, deeply nested input objects, no annotations, and no output schema, the description is thin. It never explains how to choose among csv/json/text/file/files, what the permits array must contain, or what the result reports, which are the decisions an agent must make before calling.

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% across 17 parameters, so the description needs to compensate and largely does not. It mentions asOf and the "warning window" (presumably expiryWarningDays) and that permits are caller-supplied, but leaves unexplained the csv/json/text/file/files input-mode alternatives, the permits record fields (expiresAt, permitNumber, authority), and the many unrelated parameters in the schema.

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 names a specific verb and resource ("Check ... environmental permit expiry dates") and constrains the scope to caller-supplied data, which is clearly distinct from siblings such as carbon-report-consistency-check or waste-manifest-reconcile. It also draws a useful boundary with "Compliance determinations are not made." It stops short of naming an alternative tool explicitly, so it is clear but not fully sibling-differentiated.

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?

"Compliance determinations are not made" implicitly tells the agent this is not a compliance-verdict tool, and the price/402 note gives operational context. However, there is no explicit when-to-use or when-to-prefer-a-sibling guidance, and no statement of what inputs are required to make the check meaningful.

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