Skip to main content
Glama

Edit invoice in CrewNest

crewnest_edit_invoice
Read-onlyIdempotent

Edit 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_edit_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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description adds value by confirming it 'opens nothing by itself' and only returns screens, buttons and fields. It does not explain what happens when the user's plan or permissions block the edit, but the key behavioral contract (guidance-only, no side effects, requires a follow-up browser tool) is disclosed.

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, describing the guidance-then-browser workflow. The third sentence about CrewNest's official Job Pricing MCP server is an off-topic tangent that dilutes focus and could confuse an agent about which API applies to invoice editing.

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 must describe the return content, and it does so concretely ('step by step (screens, buttons, fields)'). The only shortfall is the unrelated API sentence, which adds noise rather than missing information.

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 the schema carries nothing to explain and the baseline is 4. The description correctly implies there is nothing to pass, consistent with the empty input schema.

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 states a specific verb and resource ('Edit invoice in the user's own CrewNest account') and clarifies that the tool returns step-by-step instructions rather than performing the edit. This makes it distinguishable from a pure instruction-less action tool, though it never contrasts purpose against nearby siblings such as crewnest_create_invoice or crewnest_edit_estimate.

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?

Guidance is implied through the two-step workflow: call this tool to obtain the steps, then act via the cotlet_browser_* tools in the Cloud Browser. There is no explicit when-not-to-use, no prerequisites, and no routing versus sibling invoice tools; the closing sentence about the official Job Pricing MCP server is unrelated and does not help select this tool.

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