Skip to main content
Glama
Sign In
rb209-mcp

rb209-mcp

by charles-gentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rb209_advice_note_arable_eng_wal

Retrieve the full list of available advice notes for arable farming in England and Wales to support RB209 nutrient management planning.

Instructions

GET /api/AdviceNote/ArableEngWal — The full list of available advice notes for England and Wales arable.

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": "rb209_advice_note_arable_eng_wal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a GET operation returning a full list, implying a read-only behavior, but it does not describe response format, ordering, or any other behavioral traits. This is acceptable for a trivial 0-parameter list endpoint but still minimal.

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?

The description is a single sentence with the endpoint method and path front-loaded, followed by a precise scope. There is no wasted text or redundant repetition of the tool name.

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?

For a 0-parameter list endpoint with no output schema, the description communicates the core return value: the full list of advice notes for England and Wales arable. It does not describe the structure of each advice note, but this is not essential for selecting and invoking this simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema coverage is 100%, so there is no parameter documentation burden. The description adds context that this is an unfiltered 'full list' endpoint, which is sufficient.

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 states a specific resource (GET /api/AdviceNote/ArableEngWal) and a precise scope: the full list of advice notes for England and Wales arable. This clearly distinguishes it from siblings like rb209_advice_note_arable_scot, rb209_advice_note_grass_eng_wal, and rb209_advice_note_grass_scot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'England and Wales arable' qualifier gives clear context for when this tool is appropriate. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent from sibling names.

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

Deploy Server

Other Tools