Skip to main content
Glama
Sign In
rb209-mcp

rb209-mcp

by charles-gentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rb209_arable_potato_groups

Retrieves the list of potato groups needed for arable potato crops, allowing selection of the correct group for nutrient planning.

Instructions

GET /api/Arable/PotatoGroups — The full list of available potato groups (only required for arable potato crops).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

There are no annotations, so the description carries the burden of disclosing behavior. It clearly communicates a read-only list retrieval via 'GET' and 'full list,' which implies no side effects. The scope qualifier about arable potato crops adds useful behavioral context beyond the endpoint itself.

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 efficient sentence with no filler. It front-loads the endpoint and core purpose, then adds the relevant usage qualifier.

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 simple zero-parameter list endpoint, the description provides enough information to select and invoke the tool. It does not describe the shape of the returned potato group objects, but without an output schema and given the low complexity, this is a minor gap rather than a blocking omission.

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, so the empty schema fully covers invocation. The description does not need to explain parameter semantics, and the baseline of 4 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 GET endpoint for 'the full list of available potato groups,' which names the resource and action precisely. The phrase 'potato groups' and 'full list' distinguish it from singular-item and variety-related siblings such as rb209_arable_potato_group and rb209_arable_potato_varieties.

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 parenthetical 'only required for arable potato crops' gives a clear usage context and implies this lookup is not needed for other crop types. It does not explicitly name alternative tools or provide a when-not-to-use statement, so it stops short of a 5.

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