Skip to main content
Glama

Pay customer invoice in CrewNest

crewnest_pay_customer_invoice
Read-onlyIdempotent

Pay customer 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_pay_customer_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, and the description stays consistent with them while adding real context: the tool performs no action itself ('opens nothing by itself') and requires a separate browser toolchain to execute the payment. That resolves what would otherwise be a confusing name-versus-behavior gap. It stops short of describing the shape or length of the returned guidance or any account/prerequisite checks.

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 first two sentences are well ordered and front-load the actual behavior. The third sentence about CrewNest's official Job Pricing MCP server with three read-only pricing tools is unrelated promotional content that does not help an agent select or invoke this tool, and 'from ChatGPT, Claude or any AI agent' is pure filler. Roughly a third of the text does not earn its place.

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, no output schema, and fully populated annotations, the description carries only the burden of explaining what comes back and what happens next — and it does both ('step by step screens, buttons, fields' and hand off to cotlet_browser_*). Only the surrounding workflow preconditions (e.g., which invoice, sign-in state) are left implicit.

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 no parameters and the schema is an empty closed object, so there is nothing for the description to disambiguate — baseline 4 applies. The description correctly implies no input is needed, only an implicit 'user's own CrewNest account' context.

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 second sentence gives a concrete, verifiable function: it 'Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself.' That is specific enough to distinguish it from action-performing siblings. The opening phrase 'Pay customer invoice' overstates the action and only gets corrected one clause later, which costs it the top score.

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 states a clear follow-on path: after reading the steps, perform them 'with the cotlet_browser_* tools in the user's CrewNest Cloud Browser.' That is genuine routing guidance. However, it gives no when-not-to-use conditions relative to the listed siblings that touch invoices (crewnest_get_payment_link, crewnest_get_payment_setup_status, crewnest_send_invoice), so the agent must infer which invoice/payment entry point applies.

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