Skip to main content
Glama

Create invoice in CrewNest

crewnest_create_invoice
Read-onlyIdempotent

Create 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_create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With annotations declaring readOnlyHint=true and destructiveHint=false, the description usefully explains the apparent mismatch: the tool only returns screens/buttons/fields guidance and 'opens nothing by itself,' so nothing is mutated. It also discloses the two-step execution model via external browser tools, which is real behavioral context beyond the annotations. It stops short of describing the size or reliability of the returned guidance.

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 functional content is two sentences, but the closing sentence about CrewNest's separate free Job Pricing MCP server with three read-only tools is unrelated promotional filler that does not help an agent invoke this tool. The 'from ChatGPT, Claude or any AI agent' phrasing is also marketing padding, and the misleading opener forces the reader to re-parse the purpose mid-paragraph.

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-parameter, annotation-rich tool with no output schema, the description supplies the essential missing pieces: what is returned (step-by-step screens, buttons, fields), that nothing is executed, and which tools actually perform the action. It could be more complete by noting whether it returns static instructions or account-specific ones, but it is sufficient to call correctly.

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 (empty object, additionalProperties false), so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly implies no inputs are needed by characterizing the tool as a pure guidance response.

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 description opens with 'Create invoice in the user's own CrewNest account,' which reads as a write operation, then reverses course by saying it 'Returns how to do it in CrewNest step by step... and opens nothing by itself.' The actual purpose (produce a how-to guide) is only clear after the second clause, and it is not distinguished from siblings such as crewnest_edit_invoice or crewnest_send_invoice that presumably do act on invoices.

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 hand-off: use the cotlet_browser_* tools in the CrewNest Cloud Browser to perform the action after reading the steps. However, it never says when this tool should be chosen over sibling invoice tools, nor when it should be skipped, leaving the alternative-selection decision implicit.

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