kilimo-mcp

fertilizer_guide

Get fertilizer recommendations for Kenyan crops based on soil type.

Instructions

Fertilizer recommendations by Kenya crop and soil type. DEMO.

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": {
      "crop": "<crop>"
    },
    "name": "fertilizer_guide"
  }
}

Input Schema

Name	Required	Description	Default
`crop`	Yes
`soil_type`	No		medium

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 7, 2026

TDQS

B3/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 burden. It only discloses that it is a 'DEMO', which hints at limited functionality, but offers no information about read-only behavior, data sources, or any side effects. This minimal disclosure leaves many behavioral aspects unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise phrase with no wasted words. It is front-loaded and easy to skim. However, it is so brief that it sacrifices useful detail, though this is more a completeness concern than a conciseness flaw.

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?

The tool is simple with only 2 parameters and an output schema, which mitigates the need for extensive return-value documentation. Still, the description gives only a high-level purpose and does not explain how to use the parameters or any limitations beyond 'DEMO'. It is minimally sufficient but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. It mentions 'crop' and 'soil type', matching the two parameters, but provides no details about accepted values, defaults, or the meaning of the 'medium' default for soil_type. This is inadequate for guiding an agent on what to pass.

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 tool's function: providing fertilizer recommendations based on Kenya crop and soil type. It distinguishes itself from siblings like crop_calendar or input_cost_calculator by focusing on fertilizer recommendations. However, it lacks an explicit verb like 'provides' or 'recommends', making it slightly less direct.

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?

Usage is implied: if you need fertilizer recommendations for Kenyan crops, this is the tool. There is no explicit guidance on when not to use it or alternatives, but the sibling tools cover different areas (pests, market timing, costs), so the differentiation is clear enough.

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

Deploy Server