Skip to main content
Glama

Send invoice in CrewNest

crewnest_send_invoice
Read-onlyIdempotent

Send invoice 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_send_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered structurally. The description adds genuinely new behavioral context the annotations cannot convey: the tool 'opens nothing by itself' and only returns instructional content, with the real action delegated to cotlet_browser_* tools. That prevents an agent from treating a successful call as a completed send. It stops short of describing pagination, failure modes, or what happens when the user is not authenticated.

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 disclosure is front-loaded and useful, but the text is padded with promotional framing ('from ChatGPT, Claude or any AI agent') and a closing sentence about CrewNest's Job Pricing MCP server that has no bearing on invoking this tool. That final sentence does not earn its place and dilutes an otherwise tight two-sentence core.

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 zero parameters and no output schema, the description carries most of the burden, and it does describe what comes back ('screens, buttons, fields' in step-by-step form) plus the absence of side effects. An agent can call this correctly without further information. The unrelated API sentence is noise rather than a missing piece, so completeness is slightly imperfect rather than deficient.

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; the baseline of 4 applies. The description correctly avoids inventing parameter semantics and instead focuses on the return behavior, which is the only thing an agent needs to reason about here.

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 (send invoice in the user's CrewNest account) and immediately qualifies it: the tool returns step-by-step UI instructions rather than performing the send. That qualification is essential to understanding what the tool actually does. It does not, however, distinguish itself from siblings like crewnest_send_estimate or crewnest_send_payment_receipt, which share the same 'send X in CrewNest' shape.

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 downstream workflow cue ('then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which tells the agent how this tool fits into a sequence. But there is no explicit when-to-use versus when-not, and no guidance on choosing between this and the near-identical send_estimate or send_payment_receipt tools. Usage is implied through workflow context rather than stated.

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