Skip to main content
Glama

Estimate BNG income

estimate_bng_income
Read-only

Estimate 30-year lump-sum BNG income (LOW/MID/HIGH) for dedicating area_ha hectares of an England parcel to biodiversity net gain habitat creation, from LandBNG planning assumptions per habitat capped at the Defra statutory credit price; local factors (flood zone, SSSI, Green Belt, Ancient Woodland, AONB, Agricultural Land Class, nearby NSIP projects and how many fall under mandatory BNG) are listed, not priced. England only. Free, no key.

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": {
      "lat": "<lat>",
      "lon": "<lon>",
      "area_ha": "<area_ha>"
    },
    "name": "estimate_bng_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
area_haYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds substantive behavior beyond the readOnlyHint annotation: the estimate is capped at the Defra statutory credit price and derived from LandBNG planning assumptions per habitat, and it explicitly discloses a limitation – local factors (flood zone, SSSI, Green Belt, AONB, Agricultural Land Class, nearby NSIP projects) are listed but NOT priced. That 'listed, not priced' caveat is exactly the kind of expectation-setting an agent needs. It falls short of 5 only because it doesn't mention confidence/uncertainty of the scenario bands or failure modes for out-of-England coordinates.

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?

One dense, front-loaded passage with no filler; the geography and cost caveats follow logically after the core verb+resource statement. The parenthetical list of local factors is long but earns its place by defining the tool's output boundary.

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

Completeness4/5

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

An output schema exists, so return structure needn't be explained, and the description correctly spends its budget on pricing model, scenario bands, and the geography gate. The remaining gap is coordinate semantics for lat/lon on a tool with zero schema parameter documentation.

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 all three parameters are undocumented in the schema. The description rescues `area_ha` by tying it to hectares dedicated to habitat creation and implies the lat/lon pair denotes an England parcel, but it never states coordinate conventions, precision, or valid bounds. Partial compensation only.

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?

Names a specific verb (estimate) and resource (30-year lump-sum BNG income in LOW/MID/HIGH bands) with clear scope: `area_ha` hectares of an England parcel. The income-vs-cost distinction from the sibling `estimate_bng_cost` is implied by the wording but never stated explicitly, so an agent must infer the contrast from the word 'income' alone.

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?

Gives hard preconditions – England only, free, no key required – which is useful gating, but offers no explicit when-to-use / when-not-to-use guidance relative to `estimate_bng_cost` or `check_grid_connection`. The agent must deduce applicability from geography and the noun 'income'.

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