Skip to main content
Glama

assess_journey_risk

Read-only

Composite journey risk from weather + routing + road; persists when tenant is known.

Tenant resolution order: explicit api_key arg → request ContextVar (X-API-Key on /mcp)
→ default demo tenant when persistence is on.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "assess_journey_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
api_keyNo
profileNosafest
activityNoroad_trip
destinationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and non-destructive behavior. The description adds persistence behavior and tenant resolution order, including api_key and ContextVar fallback, which is useful operational context beyond the annotations. It does not detail output or rate limits, but an output schema exists.

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?

Two sentences, front-loaded with purpose, then tenant resolution. Dense but no filler; it could be slightly clearer by separating persistence from resolution.

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?

Given complex nested inputs and no schema descriptions, the definition is incomplete on parameter meaning and usage. It does cover persistence and tenant behavior, and the output schema exists, so return values need not be described.

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 coverage is 0% and five parameters include nested origin/destination objects plus profile and activity defaults. The description only explains api_key's role in tenant resolution; it leaves origin, destination, profile, and activity semantics undocumented.

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 it computes a composite journey risk from weather, routing, and road data, which is a specific resource and operation. It does not explicitly distinguish itself from siblings like analyze_weather_risk or get_route_conditions, so sibling differentiation is missing.

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?

No guidance is given on when to choose this tool over analyze_weather_risk, get_route_conditions, or optimize_route. The only conditional text concerns tenant resolution, not usage selection.

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.