Skip to main content
Glama

Roof rainwater capture

bpj_material_water_capture
Read-onlyIdempotent

Estimate water collected from a rain event using horizontal catchment area and a supplied runoff coefficient.

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": {
      "area": "<area>",
      "rain": "<rain>",
      "coefficient": "<coefficient>"
    },
    "name": "bpj_material_water_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
rainYes
coefficientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that this is an estimate derived from two physical inputs, but says nothing about the result's units or whether the estimate is a pure closed-form calculation.

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?

A single well-formed sentence with no filler, front-loading the verb and resource before the inputs. Every clause earns its place.

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 three-parameter closed-form calculator with no output schema, the description leaves the return value's units (litres, m3) and the runoff-coefficient domain (0-1, per the schema) unexplained. The core operation is clear, but a caller cannot predict the magnitude or units of the output from the text alone.

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 carry the burden and it only partly does: 'horizontal catchment area' clarifies the area parameter and 'runoff coefficient' clarifies the coefficient, but the naming mismatch with the schema title 'Collection coefficient' is unaddressed and the 'rain' parameter receives no explanation. Meaning is added for two of three parameters, but not enough to fully compensate for zero schema coverage.

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 ('Estimate') and resource ('water collected from a rain event') and scopes it to horizontal catchment area plus a runoff coefficient, which cleanly distinguishes it from the numerous material-quantity siblings. It stops short of naming any alternative tool, so a 5 is not warranted.

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 statement of when to use this tool versus alternatives, no prerequisite conditions (e.g. that the coefficient must already be known for the roof material), and no exclusions. The phrase 'supplied runoff coefficient' only weakly implies the caller must source that value externally.

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.