rb209-mcp

rb209_rainfall_summer_rainfall_average

Get average field rainfall for summer months (April-September) using a UK postcode to inform nutrient management decisions.

Instructions

GET /api/Rainfall/SummerRainfallAverage/{postcode} — Average rainfall of the field during the summer months (April - September).

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": {
      "postcode": "<postcode>"
    },
    "name": "rb209_rainfall_summer_rainfall_average"
  }
}

Input Schema

Name	Required	Description	Default
`postcode`	Yes	First half of postcode, eg: AB12

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does convey that this is a read-only GET operation and specifies the covered months, but it does not describe response format, units, or any edge-case behavior.

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 sentence conveys the HTTP method, endpoint path, and semantic definition. It is front-loaded with the route and contains no redundant information.

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 one-parameter GET lookup, the description gives a reasonable high-level understanding. However, there is no output schema and no note about the response value's format or units, so the agent is left inferring what 'average rainfall' means as a return value.

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?

The schema already documents the single 'postcode' parameter with a format example, so the description adds little beyond showing it appears in the URL path. Schema coverage is 100%, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific GET resource and its purpose: returning average rainfall during summer (April–September). This distinguishes it from the sibling winter rainfall average tool and the generic rainfall average tool.

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?

The description implies usage by naming the season and months, but it does not explicitly say when to use this tool over the winter or generic rainfall siblings. No alternatives or exclusion conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server