Skip to main content
Glama

Routing Driving Risk Tool

routing-driving-risk
Read-only

Reads a local business day route and high driving-risk stops for the authenticated workspace without exposing addresses or private route notes. Use to inspect routing and driving risks in the connected business. Returns date, timezone, routes, anomalies, summary, scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "routing-driving-risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal business date, YYYY-MM-DD; defaults to today.
limitNoMaximum route stops to return.
technician_idNoOptional technician filter.

Output Schema

NameRequiredDescriptionDefault
dateYesDate used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
routesYesBounded routes records returned by this tool.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.
timezoneYesTimezone used or returned by this tool.
anomaliesYesBounded anomalies records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "anomalies": {
      +      "description": "Bounded anomalies records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "date": {
      +      "description": "Date used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "routes": {
      +      "description": "Bounded routes records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "timezone": {
      +      "description": "Timezone used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "timezone",
      +    "routes",
      +    "anomalies",
      +    "summary",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add a real behavioral constraint not in the annotations – that addresses and private route notes are never exposed – which is genuinely useful for an agent reasoning about output sensitivity. However it says nothing about cost, pagination, or what happens when no route exists, so it adds one good detail rather than rich behavioral context.

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?

Three short sentences, front-loaded with the read verb and resource before the usage note. The final sentence enumerating return fields (date, timezone, routes, anomalies, summary, scope) is partly redundant given the output schema exists, costing it a point.

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

Completeness4/5

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

With an output schema present, the description needn't explain return values, and it correctly defers parameter detail to a fully-documented schema while still stating the privacy boundary. What's missing is only minor: no indication of empty-result behavior or how anomalies are determined.

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?

Schema description coverage is 100% and each of the three optional parameters (date default-to-today, limit capped at 50, technician_id filter) is fully documented in the schema. The description adds no parameter meaning of its own, so the baseline 3 applies.

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?

States a concrete verb ("Reads") plus the resource ("local business day route and high driving-risk stops") and scopes it to the authenticated workspace, which is enough for an agent to tell it apart from the CRM/reporting siblings. It stops short of naming a specific alternative, but the resource is narrow enough that confusion is unlikely.

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?

"Use to inspect routing and driving risks in the connected business" gives an implied use case but no when-not conditions, prerequisites, or pointers to a related sibling. Guidance is adequate but thin.

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.

Resources