Service Autopilot MCP Server and API by Cotlet

List invoices in Service Autopilot

service_autopilot_list_invoices

Read-onlyIdempotent

List invoices in the user's own Service Autopilot account from ChatGPT, Claude or any AI agent. Returns how to do it in Service Autopilot step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Service Autopilot Cloud Browser. Service Autopilot's official API: Service Autopilot has no public API, developer portal or self-service API keys (checked 11 Oct 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": "service_autopilot_list_invoices"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely non-obvious context: it 'opens nothing by itself', requires a follow-up browser tool chain, and Service Autopilot has no public API (no developer portal or self-service keys). It does not describe the shape of the returned steps beyond 'screens, buttons, fields'.

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 purpose and the follow-up workflow are front-loaded, but sentences are long and run together, and the 'from ChatGPT, Claude or any AI agent' framing carries no decision value for an agent. The API note is useful but appended in a compressed, awkward clause.

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?

For a simple, parameterless, read-only guide tool with no output schema, the description covers what it returns, what it does not do, and what the agent must do next. The only gap is any hint about the granularity or format of the returned steps.

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 with an effectively closed object schema, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool 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 specific verb and resource ('List invoices in the user's own Service Autopilot account') and immediately clarifies that it returns step-by-step instructions rather than the invoices themselves, which disambiguates an otherwise misleading name. It does not, however, differentiate itself from the generic sibling cotlet_app_guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage path: call this to obtain the procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. It omits any explicit when-not-to-use condition or comparison against cotlet_app_guide, so an agent must infer which guide tool to pick.

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

All Service Autopilot 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?