FieldRoutes MCP Server and API by Cotlet

List unpaid tickets in FieldRoutes

fieldroutes_list_unpaid_tickets

Read-onlyIdempotent

List unpaid tickets 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_unpaid_tickets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description does add material context beyond that: it opens nothing by itself and returns screens/buttons/fields. But the FieldRoutes official-API and 50-requests-per-day detail is about a different access path and adds noise rather than behavior for this tool.

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?

Front-loaded with the purpose and the key 'opens nothing by itself' caveat. The trailing API-key/rate-limit sentence is tangential to this tool and slightly dilutes the message, but the overall structure is tight for three sentences.

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?

No output schema exists, and the description compensates by describing the return shape (step-by-step screens, buttons, fields) and the handoff to browser tools. For a zero-parameter read-only guidance tool, that covers what an agent needs before calling it.

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 has zero parameters and the schema is fully closed (additionalProperties: false), so there is nothing to explain. The baseline of 4 applies; the description correctly implies there are no inputs to supply.

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 the resource (unpaid tickets in the user's FieldRoutes account) and clarifies the actual operation: it returns step-by-step instructions rather than the data itself. The first phrase 'List unpaid tickets' is nominally a verb+resource, but the real behavior is a how-to guide, which the second sentence corrects. It's clear enough, though the title/name vs. actual behavior gap costs it a point.

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 says to use the cotlet_browser_* tools in the user's FieldRoutes Cloud Browser after getting the guide, which is genuine routing guidance. However, it never says when NOT to use it, nor how it relates to other FieldRoutes tools like fieldroutes_list_customers, and the role of cotlet_app_guide is left implicit.

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?