Skip to main content
Glama

Export invoices in CrewNest

crewnest_export_invoices
Read-onlyIdempotent

Export 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_export_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description usefully reinforces that nothing is opened or mutated by the call itself. Beyond that, it adds little about the returned content's shape, and the trailing sentence about an unrelated official Job Pricing MCP server adds confusion rather than behavioral clarity.

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 first two sentences are front-loaded and earn their place, but the final sentence about CrewNest's official Job Pricing MCP server has nothing to do with exporting invoices and dilutes the call to action. Roughly a third of the text is off-purpose.

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 zero-param, read-only guidance tool with no output schema, the description states what comes back (step-by-step screens, buttons, fields) and what to do next. Only the exact return format and any account/permission prerequisites are left unstated.

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?

Zero parameters, so the schema carries no semantics to supplement and the baseline of 4 applies. The description correctly implies a parameterless, informational call.

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 specifies the resource (invoices) and, crucially, clarifies that the tool does not itself export: it "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." That distinguishes it from the cotlet_browser_* execution tools, though the name 'export_invoices' still reads like the action itself and no sibling such as crewnest_list_invoices is contrasted.

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?

It gives an explicit two-step flow: call this to get instructions, then perform the export via cotlet_browser_* in the user's CrewNest Cloud Browser. No exclusions or preconditions (plan tier, auth) are stated, and it does not say when to prefer listing invoices over exporting, but the routing guidance is concrete.

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