Skip to main content
Glama

Get dashboard in CrewNest

crewnest_get_dashboard
Read-onlyIdempotent

Get 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_get_dashboard"
  }
}

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 by structured data. The description adds genuinely new context on top: despite the verb "Get", nothing is opened or navigated, and the return payload is instructional content (screens, buttons, fields). It does not describe length or formatting of that output, but the key behavioral surprise is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The functional content fits in roughly two sentences, but the definition opens with padded phrasing ("from ChatGPT, Claude or any AI agent") and closes with an entirely off-topic paragraph advertising CrewNest's separate Job Pricing MCP server. That last sentence consumes a third of the text without helping an agent decide or invoke anything, so the definition is not front-loaded cleanly.

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?

For a zero-parameter, read-only instruction tool with full annotation coverage and no output schema, the description gives the agent what it needs: it says instructions come back instead of an opened dashboard, and it names the follow-up tool family to execute them. Completeness is only marginally reduced by the absence of any note on output length or failure modes.

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 (empty object, additionalProperties false), so there are no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents the argument surface.

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?

"Get dashboard in the user's own CrewNest account" states a specific resource, and the second sentence corrects the likely misreading of the name by clarifying it "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." That is a clear description of what the tool returns. It does not name or distinguish itself from nearby siblings such as crewnest_open_payout_dashboard, so it stops short of a 5.

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 implies the workflow — call this to obtain navigation steps, "then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser" — which is a useful hand-off instruction. However, it never states when to prefer this over dashboard-related siblings or what preconditions apply (e.g., being signed in). Usage is implied rather than explicitly scoped.

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