Skip to main content
Glama
Sign In
rb209-mcp

rb209-mcp

by charles-gentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rb209_advice_note_advice_notes

Get the complete list of available RB209 advice notes to access nutrient management guidance for crop planning and soil fertility decisions.

Instructions

GET /api/AdviceNote/AdviceNotes — The full list of available advice notes.

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_advice_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It reveals that this is a GET-style operation returning all advice notes, but it does not disclose response shape, ordering, pagination, authentication requirements, or any side effects. This is thin coverage for a tool with no output schema.

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 one compact line, front-loads the endpoint, and adds a plain-language gloss. Every part earns its place; there is no redundancy.

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 parameterless list endpoint, the description is minimally viable: it names the resource and the fact that it returns the full list. However, there is no output schema and no guidance on how the returned items relate to sibling tools, so an agent does not know what fields or identifiers to expect.

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 input schema has zero parameters, so schema description coverage is trivially 100% and the description cannot add parameter-level meaning. Per the baseline for no-parameter tools, this is adequate.

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 resource ('AdviceNote/AdviceNotes') and states that it returns 'the full list of available advice notes,' so the core purpose is clear. It does not explicitly differentiate itself from sibling collection tools, but 'full list' and the endpoint resource make it distinguishable from singular/detail tools like rb209_advice_note or rb209_advice_note_text.

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?

The description provides no guidance on when to use this tool versus alternatives, and no mention of related tools such as rb209_advice_note or rb209_advice_note_text for retrieving details. 'The full list' implies selection for enumeration, but that is left to inference rather than stated.

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