Skip to main content
Glama

Manage payment connection in CrewNest

crewnest_manage_payment_connection
Read-onlyIdempotent

Manage payment connection 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_manage_payment_connection"
  }
}

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 and destructiveHint=false, so the safety profile is covered. The description still adds genuinely non-obvious behavior: it 'opens nothing by itself' and only returns instructions, and the real action happens through a separate cotlet_browser_* tool family — exactly the kind of context annotations cannot convey. It stops short of saying what happens if a connection already exists or whether the user must be logged in.

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, stating the deliverable and the handoff to browser tools. The third sentence about CrewNest's official Job Pricing MCP server and its three read-only price-calculation tools is unrelated to this tool and reads as promotional filler that dilutes the routing signal.

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-param, no-output-schema guidance tool, the description covers what is returned (step-by-step screens/buttons/fields) and how to act on it. It omits how to tell whether a connection already exists and does not separate itself from the payment status/link siblings, which leaves a real ambiguity for the agent.

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 there is no parameter semantics for the description to compensate for; the baseline for a 0-param tool applies. Nothing in the description misdescribes inputs.

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 makes the actual deliverable concrete: it 'Returns how to do it in CrewNest step by step (screens, buttons, fields)' for a payment connection in the user's own account. That is far more specific than the vague verb 'manage' in the name. It does not, however, distinguish itself from close siblings such as crewnest_get_payment_setup_status or crewnest_get_payment_link, which an agent could plausibly pick instead.

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 — use the cotlet_browser_* tools in the Cloud Browser to actually perform the steps — which is useful workflow context. But there is no when-not guidance and no explicit routing away from the payment-status or payment-link siblings, so the agent must infer which payment tool to call first.

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