Skip to main content
Glama

Open payout dashboard in CrewNest

crewnest_open_payout_dashboard
Read-onlyIdempotent

Open payout dashboard 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_open_payout_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, and the description is consistent with them by stating nothing is opened or changed. It adds genuinely useful context beyond the annotations by disclosing the return shape ('step by step (screens, buttons, fields)') and the handoff to browser tools for execution.

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 tight and front-load the important scope and read-only caveat. The third sentence, promoting CrewNest's separate free Job Pricing MCP server with three read-only tools, is unrelated to selecting or invoking this tool and is wasted space that dilutes the definition.

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 parameters, no output schema, and read-only annotations, the description carries the modest remaining burden, and it does explain what comes back (stepwise UI instructions) and what the agent should do next. The only shortfall is the absence of any note on how the returned instructions should be presented or whether the dashboard requires specific account permissions.

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 meaning for the description to supply, and the schema closes the object with additionalProperties=false. Baseline for a parameterless tool applies; the description neither helps nor harms here.

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 names a specific action ('Open payout dashboard') and a specific resource/scope ('in the user's own CrewNest account'), then immediately qualifies it by stating it 'opens nothing by itself,' so the agent learns this is an instruction-returning tool, not a mutation. This partial tension between the imperative name and the actual behavior is clarified in-text, which keeps it from being misleading, though the wording could front-load the read-only nature more cleanly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent to a follow-up path: 'then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser,' naming the correct alternative for actually performing the action. It lacks an explicit statement of when to prefer a sibling like crewnest_get_dashboard instead, so it stops short of a full when/when-not treatment.

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