Skip to main content
Glama

Get payment setup status in CrewNest

crewnest_get_payment_setup_status
Read-onlyIdempotent

Get payment setup status 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_setup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: it 'opens nothing by itself' and returns screens, buttons and fields, which matters because there is no output schema. That value is partly undercut by the closing sentence about an unrelated free Job Pricing MCP server, which discloses nothing about this tool's behavior.

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 the no-side-effects/next-step clauses are front-loaded and earn their place. The final sentence promoting CrewNest's separate Job Pricing MCP server is off-topic filler that does not help an agent decide or invoke this tool, and it dilutes an otherwise compact 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?

With zero params, no output schema, and annotations covering the safety profile, the description does cover the return shape and the follow-up tooling. The gap is conceptual: it is unclear whether the call inspects the account's actual configuration or only emits generic instructions, which is the key thing an agent needs to know before calling it. The promotional tail adds no completeness.

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 nothing for the description to disambiguate beyond the schema. Baseline 4 applies; no parameter meaning is missing or misstated.

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?

Names a specific verb and resource (get payment setup status) and scopes it to the user's own CrewNest account. It then clarifies that what is actually returned is step-by-step how-to content rather than a live status value, which is a useful disambiguation but slightly muddies the stated purpose. It does not name a sibling to contrast with, so differentiation from crewnest_manage_payment_connection or crewnest_get_payment_link is left implicit.

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 clear downstream path ('then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which functions as a next-step alternative. However, it never states when to prefer this over the other payment-related siblings, nor any precondition such as whether the user must already have a payment connection configured.

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