rb209-mcp

rb209_fertiliser_prices_request_access

Request access to fertiliser price data by providing a reason, enabling nutrient planning tools to retrieve current prices.

Instructions

POST /api/FertiliserPrices/RequestAccess — Request access to the fertiliser latest prices endpoint.

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": {
      "body": "<body>"
    },
    "name": "rb209_fertiliser_prices_request_access"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Request access.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It identifies this as a POST request-access action but does not explain side effects, authentication requirements, approval process, response behavior, or whether calling it multiple times has different effects. The behavioral surface is opaque 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 front-loaded sentence that conveys the HTTP method, endpoint, and purpose with no filler. Every part of the sentence earns its place.

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?

This is a low-complexity tool with one optional parameter and no output schema. The description is minimally viable, but it lacks any note about the relationship to the latest-prices endpoint or what a successful access request returns. Given the simple shape, this is acceptable but not strong.

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 provides 100% coverage of the single body parameter, including a description for 'reason'. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 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 states a specific verb ('Request access') and a specific resource ('fertiliser latest prices endpoint'), and includes the HTTP method and endpoint path. This makes the tool's purpose immediately clear and distinct from the sibling rb209_fertiliser_prices_latest_prices, which is about retrieving prices rather than requesting access to them.

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 gives no guidance on when to use this tool, whether it is a prerequisite for rb209_fertiliser_prices_latest_prices, or what conditions should trigger an access request. It does not mention alternatives or exclusions, leaving the agent to infer the usage context.

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

Deploy Server