Skip to main content
Glama

Record payment in CrewNest

crewnest_record_payment
Read-onlyIdempotent

Record payment 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_record_payment"
  }
}

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, so the safety bar is low. The description still adds real value by resolving the name/annotation tension: it explicitly says the tool 'opens nothing by itself' and returns screens, buttons and fields, which tells the agent the operation is a dry explanation with a separate execution step. The closing sentence about an unrelated Job Pricing MCP server adds no behavioral information about this tool.

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 dense and front-load the key facts about what is returned and what is not executed. The third sentence pivots to CrewNest's separate free Job Pricing MCP server, which is promotional context unrelated to recording a payment and dilutes focus.

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 no input parameters, no output schema and safety fully covered by annotations, the definition supplies the one thing an agent actually needs: the return shape (step-by-step screens, buttons, fields) and the handoff to browser tools. The off-topic API sentence is noise rather than an omission, so completeness is good.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing beyond the schema to explain and the baseline of 4 is exceeded only by not introducing confusion; the description correctly implies the tool is callable with no arguments. No parameter meaning is missing.

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 does name a specific resource and reframes the tool as returning step-by-step how-to guidance rather than performing the payment. However, the opening verb 'Record payment' reads like an action and the actual behavior (returns instructions, opens nothing) only becomes clear in the second sentence, so an agent must read past a misleading first impression. No sibling is named to distinguish it from crewnest_get_payment_link or crewnest_send_payment_receipt.

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 follow-on path: after getting the steps, execute them with the cotlet_browser_* tools in the Cloud Browser. That is implied usage guidance rather than explicit when-to-use guidance, and it never states when an agent should prefer this tool over the payment-related siblings.

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