Skip to main content
Glama
Sign In
rb209-mcp

rb209-mcp

by charles-gentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rb209_advice_note

Retrieve the full text of an RB209 advice note using its unique advice note code. Access the corresponding nutrient management guidance directly.

Instructions

GET /api/AdviceNote/AdviceNote/{adviceNoteCode} — Individual advice note text filtered from the supplied corresponding advice note code.

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": {
      "adviceNoteCode": "<adviceNoteCode>"
    },
    "name": "rb209_advice_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
adviceNoteCodeYesThe advice note code to filter on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

The GET method and 'Individual advice note text' disclose the primary read-only behavior and the general return content. With no annotations and no output schema, the description does not cover error behavior, exact response format, or assumptions about the code value.

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 method and path front-loaded and no filler. It is compact and directly communicates the tool's purpose.

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 lookup, the description is nearly sufficient: it names the endpoint, the method, and the parameter's role. It is incomplete in that it does not differentiate the many advice_note sibling tools or describe the response shape, which matters because there is no output schema.

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 adviceNoteCode with 100% coverage, so the description adds little beyond what is structured. Phrases like 'supplied corresponding' reinforce the schema but do not add format, source, or example details.

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 clearly states a concrete operation: GET a single advice note text by adviceNoteCode. It is specific about the verb and resource, but it does not distinguish this tool from closely named siblings such as rb209_advice_note_text or rb209_advice_note_advice_notes.

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 it should be used when you have an adviceNoteCode and need the corresponding advice note text. However, it gives no explicit when-not guidance or alternatives, which is a gap given the large number of related sibling tools.

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