Skip to main content
Glama

get_agricultural_conditions

Read-only

Agricultural / growing-condition indicators.

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": {
      "location": "<location>"
    },
    "name": "get_agricultural_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no indication of data sources, spatial resolution, time semantics, or coverage limits of the indicators.

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

Conciseness2/5

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

The text is short, but brevity here reflects under-specification rather than efficiency. It is a bare fragment with no front-loaded action statement, so there is nothing meaningful to skim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations cover safety. But for a tool requiring a complex nested location object with zero schema documentation, the description leaves the caller without enough information to invoke it correctly.

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?

Schema description coverage is 0% for the single required `location` parameter, which is a free-form nested object with additionalProperties=true. The description does not compensate at all: it never explains the expected shape, accepted coordinate/address forms, or whether a geocode result is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase, "Agricultural / growing-condition indicators," that essentially restates the tool name without a verb or scope. It does not say what is retrieved (frost dates, soil moisture, GDD, planting windows) or how that differs from siblings such as get_route_conditions or recommend_outdoor_activities.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. An agent cannot tell from this text whether agricultural indicators should be preferred over get_current_weather or get_forecast for a given query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.