Skip to main content
Glama

Get payment link in CrewNest

crewnest_get_payment_link
Read-onlyIdempotent

Get payment link 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_get_payment_link"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description reinforces this with 'opens nothing by itself,' which is clear and consistent. It also discloses the return shape (screens, buttons, fields), which is valuable given there is no output schema.

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 sentence front-loads the purpose and the second carries the substantive workflow detail, but the closing sentence about CrewNest's official Job Pricing MCP server with three read-only tools is unrelated promotional content that does not help an agent call this tool. The 'from ChatGPT, Claude or any AI agent' clause is filler.

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?

For a zero-parameter, no-output-schema tool the description does explain what comes back, which is the main burden. However, it never clarifies what kind of 'payment link' is meant (invoice link, customer portal link, payout setup) or what happens if the user has no payment connection configured, leaving the sibling overlap unresolved.

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 schema takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is a 4.

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 verb+resource is stated ('Get payment link in the user's own CrewNest account'), but the description then redefines the output as step-by-step instructions ('Returns how to do it in CrewNest step by step (screens, buttons, fields)'), which conflicts with the name's promise of returning an actual link. A sibling named crewnest_generate_customer_portal_link exists and is never differentiated, so an agent cannot cleanly decide between them.

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 forward workflow hint: use this to learn the steps, then execute with the cotlet_browser_* tools in the Cloud Browser. That is useful sequencing, but there is no statement of when to prefer this over the other link/payment-setup siblings, and no prerequisites or exclusions.

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