Skip to main content
Glama

analyze_weather_risk

Read-only

Activity-based weather risk (e.g. outdoor_wedding) with recommendations.

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>",
      "activity": "<activity>"
    },
    "name": "analyze_weather_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
activityYes
locationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds that the analysis is activity-specific and includes recommendations, but it does not disclose limitations, assumptions, or how the recommendations are derived.

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 redundant wording and puts the activity-based framing first. However, it is so compressed that it reads as a fragment rather than a structured explanation.

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?

The tool has three parameters, a nested location object, and no schema descriptions, yet the description does not explain the required inputs. Because an output schema exists, return values need not be described, but the input-side gaps leave the definition significantly incomplete.

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%, so the description must compensate for all three parameters. It gives some meaning to the activity parameter through the outdoor_wedding example, but it does not explain the required location object, the date field, or acceptable formats.

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 states that the tool analyzes weather risk in an activity-based context and includes recommendations, with an example activity. It is clear enough to understand the resource and framing, but it does not explicitly distinguish itself from related siblings such as assess_journey_risk 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 explicit guidance on when to use this tool versus alternatives. The activity-based framing implies a use case, but the description provides no exclusions, prerequisites, or sibling routing guidance.

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.