Skip to main content
Glama

crewnest_status

Verify that your Cotlet.dev account, credits, and CrewNest connection are ready before drafting estimates or scheduling jobs.

Instructions

Check that your Cotlet.dev account and CrewNest are ready: account, credits and CrewNest connection.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It does disclose the three things being verified (account, credits, connection), which is genuine behavioral content, but it never states that the call is read-only, whether it consumes credits or triggers network/auth checks, or how failures are surfaced. For a no-annotation tool that is a meaningful gap.

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

Conciseness5/5

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

A single front-loaded sentence that names the purpose and enumerates the three checks in a compact colon list. No filler and nothing to trim.

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 no output schema, the description must convey what comes back, and it only gestures at it by listing account, credits, and connection. It does not indicate the shape of the result or what a failing check looks like, which leaves the agent under-informed about interpreting the response.

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 the baseline is 4. The description correctly adds no parameter detail because none exists, and the empty schema with additionalProperties:false is self-explanatory.

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 states a specific verb ('Check') and a specific subject: Cotlet.dev account, credits, and CrewNest connection readiness. That clearly separates it from the sibling action tools (click, close, open, read, type), which perform operations rather than report status. It stops short of explicitly naming itself as the diagnostic tool versus those siblings.

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?

Readiness-checking framing implies you run this before or when troubleshooting other CrewNest actions, but the description never says when to call it, whether it should be called first, or when it is unnecessary. Usage is inferable but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.