mcp-samsara

samsara_list_contacts

Retrieve all contacts from your Samsara fleet management account, enabling quick access to key personnel for dispatch and compliance coordination.

Instructions

List all contacts

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_contacts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

D1.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It fails to mention any behavioral traits such as whether this is a read-only operation, if it returns all contacts without filtering, pagination behavior, rate limits, or authentication requirements. The agent cannot assess side effects or constraints from this description.

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 description is extremely short (two words), but this is under-specification, not conciseness. It does not earn its place by providing value. It wastes the opportunity to inform the agent.

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

Completeness1/5

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

Given the tool has one parameter with 0% schema description coverage, no output schema, no annotations, and many sibling tools for similar entities, the description is severely incomplete. It provides no context about return values, filtering, ordering, or relationship to other resources. The agent cannot use this description reliably.

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. It only says 'List all contacts' and does not explain the 'limit' parameter's purpose, behavior (e.g., max results per page, server default), or any other parameters. The agent gets no added meaning beyond the schema's type/number/default.

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 'List all contacts' is vague. It does not specify what kind of contacts (e.g., driver contacts, customer contacts, API contacts) or any scope. It does not distinguish from sibling tools like samsara_create_contact or other list tools (list_routes, list_vehicles, list_drivers, etc.). The verb 'list' is appropriate but the resource is underspecified given the broader Samara API context.

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 versus alternatives. There is no mention of prerequisites, context, or exclusions. For example, when to list contacts vs drivers vs addresses is unclear. The description does not help the agent decide to invoke this tool over others.

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