Skip to main content
Glama

studio_ninja_status

Check Cotlet.dev account readiness, available credits, and Studio Ninja connection status before running lead, job, or billing automations.

Instructions

Check that your Cotlet.dev account and Studio Ninja are ready: account, credits and Studio Ninja 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": "studio_ninja_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?

With no annotations, the description carries the full behavioral burden. 'Check' reasonably conveys a non-mutating read, and the description discloses the three things being validated, but it says nothing about whether credits/connection checks are side-effect free, what happens on a failed check, or what the response contains (no output schema exists).

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the purpose and the three checked items arrive immediately. The colon list is slightly redundant with the word 'ready' but still earns its place by naming the concrete checks.

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, low-complexity tool this is close to complete: it states the intent and the exact items verified. The remaining gap is return-value shape, which nothing else in the definition (no annotations, no output schema) supplies.

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 to disambiguate and the baseline of 4 applies. The description correctly implies no inputs are needed by simply instructing the agent to check readiness.

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 concrete read/check operation and enumerates exactly what is inspected: account, credits, and the Studio Ninja connection. This clearly separates it from the action-oriented siblings (click, open, type, read), so an agent can tell it is a preflight status check. It stops short of a 5 only because it never says what the result looks like (e.g., boolean readiness vs. structured report).

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 framing 'Check that your ... account and Studio Ninja are ready' implies a preflight verification before invoking the action tools, which is useful implied guidance. However, there is no explicit when-to-use statement, no when-not-to-use, and no named alternative or fallback behavior if the check fails.

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