Skip to main content
Glama

List invoices in CrewNest

crewnest_list_invoices
Read-onlyIdempotent

List invoices in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The most valuable disclosure is that the tool 'opens nothing by itself' and returns procedural guidance rather than performing or fetching anything, which is genuinely additive beyond the readOnly/idempotent annotations. However, the trailing sentence about CrewNest's 'official, free Job Pricing MCP server with three read-only tools' is unrelated to invoices and muddies the behavioral picture, and the description never says whether actual invoice records come back in any form.

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 essential content is roughly two sentences, but the closing plug for the Job Pricing MCP server does not earn its place on an invoice-listing tool and risks sending the agent looking for an irrelevant alternative API. The key clarification ('opens nothing by itself') is buried mid-sentence rather than front-loaded.

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

Completeness3/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 must carry the whole burden of explaining what comes back, and it only partially does: it mentions 'screens, buttons, fields' but not format, granularity, or whether invoice data itself is included. For a zero-arg read tool the shape is simple enough that this is adequate but clearly incomplete.

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, so there is no parameter meaning to add; baseline 4 applies. The schema is fully self-describing for this shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb-and-resource framing ('List invoices in the user's own CrewNest account') sets an expectation of returned data, but a later sentence reframes the tool as one that 'Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself.' An agent gets a rough idea but must reconcile two different purposes from the same paragraph, and no sibling (e.g. crewnest_export_invoices, crewnest_create_invoice) is named to delimit scope.

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?

The description gives a concrete two-step workflow: call this to get step-by-step screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the Cloud Browser. That is usable routing guidance, though it never states when NOT to use it or which sibling list tool covers related data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources