mcp-samsara

samsara_list_drivers

Retrieve a list of every driver in your organization, including their detailed profiles and assigned external IDs, to manage fleet personnel or integrate driver records into other systems.

Instructions

List all drivers in the organization with their details and external IDs

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": "samsara_list_drivers"
  }
}

Input Schema

Name	Required	Description	Default
`after`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0-beta.1Aug 18, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description must disclose key behaviors. It only states the function but omits read-only nature, authentication requirements, rate limits, pagination behavior, or whether the list is exhaustive. The agent cannot infer important operational characteristics.

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

Conciseness3/5

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

The description is a single sentence with no fluff, but it is underspecified. While concise, it fails to include necessary details, reducing its effectiveness. It earns a middle score because it is not verbose, but not helpful enough.

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?

Given no output schema, the description should explain what 'details and external IDs' means or if the list is paginated. It does not address the 'after' parameter's role or response structure. Key contextual elements for a list endpoint are missing.

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

Parameters1/5

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

Schema description coverage is 0% and the tool description does not mention 'after' or 'limit' parameters. The agent has no semantic understanding of how to use the two optional parameters for pagination or limiting results. This is a critical gap.

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 identifies the action (list) and resource (drivers) with scope (all in organization) and output mentions (details, external IDs). It distinguishes from siblings like 'samsala_get_driver' (singular) and 'samsara_list_vehicles' (different resource). However, it does not clarify pagination implications, so it loses the top score.

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 provided on when to use this tool vs alternatives (e.g., when to use 'samsala_get_driver' for a single driver), nor any preconditions or context about pagination limits. The agent receives no help in decision-making.

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