Skip to main content
Glama
Sign In
rb209-mcp

rb209-mcp

by charles-gentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rb209_arable_crop_groups

Retrieve the complete list of arable crop groups to identify the correct category for nutrient management planning.

Instructions

GET /api/Arable/CropGroups — The full list of available crop groups.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations available, the description carries the full behavioral burden. The explicit 'GET' signals a read-only operation and 'full list' suggests there is no filtering or pagination, which is useful. Still, it does not disclose response shape, ordering, or any access constraints, so transparency is incomplete but adequate for a simple list endpoint.

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 compact sentence with the HTTP method and endpoint front-loaded, followed by a direct statement of what is returned. There is no filler or redundant explanation.

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 zero-parameter reference-list tool with no output schema, the description is largely complete: it names the endpoint, the HTTP method, and the exact scope of the response. It could describe the shape of each crop group item, but that is not necessary for an agent to select and invoke this readonly list endpoint correctly.

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 input schema is empty, so there is no parameter semantics to clarify. The 0-parameter baseline applies, and the description adds no unnecessary parameter information.

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 the action (GET) and resource (/api/Arable/CropGroups), and it specifies that the tool returns the full list of available crop groups. It does not explicitly contrast with siblings like rb209_arable_crop_group or rb209_arable_crop_types_by_group, but the plural 'groups' and 'full list' make its reference-list role reasonably clear.

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 gives clear context that this tool is for obtaining the complete set of crop groups, so usage is implied. However, it provides no explicit guidance about when not to use it or when to choose a sibling such as the singular crop group endpoint or the crop-types-by-group endpoint.

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