FieldRoutes MCP Server and API by Cotlet

List customers in FieldRoutes

fieldroutes_list_customers

Read-onlyIdempotent

List customers in the user's own FieldRoutes account from ChatGPT, Claude or any AI agent. Returns how to do it in FieldRoutes step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's FieldRoutes Cloud Browser. FieldRoutes's official API: FieldRoutes has a documented API, but keys come only through FieldRoutes support for each office, and the free tier allows 50 read requests a day per office (checked 8 Nov 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the crucial behavioral fact that the tool 'opens nothing by itself' — it produces instructions, not actions — which prevents an agent from assuming the list already happened. It also adds external constraints (API keys only via FieldRoutes support per office, 50 read requests/day free tier) that are useful context for planning.

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 core behavioral disclosure is front-loaded and clear, but the opening clause 'from ChatGPT, Claude or any AI agent' is promotional filler and the closing API-key/rate-limit sentence is tangential to invoking this specific tool. Roughly a third of the text does not earn its place.

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 no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so ('screens, buttons, fields' step by step) while also naming the tools needed to act on the result. It is complete enough for an agent to call it correctly and know the next step.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description adds no misleading hints about inputs.

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 names a specific verb and resource (list customers in the user's own FieldRoutes account) and, importantly, corrects the naive reading of the name by stating it returns a step-by-step how-to rather than a data listing. It does not explicitly distinguish itself from fieldroutes_list_unpaid_tickets or cotlet_app_guide, which keeps it from a 5.

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?

It gives a clear follow-up sequence: call this to get the procedure, then execute it with cotlet_browser_* tools in the user's FieldRoutes Cloud Browser. It offers no when-not guidance and no comparison against the sibling FieldRoutes tools or cotlet_app_guide, so selection between alternatives is left to inference.

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

All FieldRoutes MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?