Skip to main content
Glama

Send payment receipt in CrewNest

crewnest_send_payment_receipt
Read-onlyIdempotent

Send payment receipt 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_payment_receipt"
  }
}

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with all of them ("opens nothing by itself"). It adds genuine context beyond the annotations by clarifying that the output is procedural guidance rather than an executed action, and by naming the browser tools that must complete the task.

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 purpose and workflow sentences are front-loaded and efficient, but the closing sentence about CrewNest's separate free Job Pricing MCP server is unrelated to invoking this tool and does not earn its place. It is advertising noise inside a tool definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what happens (instructions returned, nothing opened) and what to do next, which is the core need for a zero-parameter, no-output-schema tool. It leaves open which payment receipt is targeted given there are no inputs, and the trailing note about an unrelated MCP server distracts rather than completes the picture.

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 and the schema is fully described, so there is no parameter semantics to explain. Baseline of 4 applies; the description correctly implies no arguments are needed.

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 first sentence states a specific verb and resource ("Send payment receipt") plus the account scope ("in the user's own CrewNest account"), so the action is unambiguous. It does not differentiate itself from adjacent siblings like crewnest_record_payment or crewnest_send_invoice, which is why it stops short of a 5.

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?

The description gives a usable workflow: the tool returns step-by-step instructions and "opens nothing by itself," after which the agent should act via the cotlet_browser_* tools. What it lacks is selection guidance among siblings — nothing says when to send a receipt versus record a payment or use a payment link.

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