Skip to main content
Glama

dribbble_status

Checks whether your Cotlet.dev account, credits, and Dribbble connection are ready before using Dribbble actions.

Instructions

Check that your Cotlet.dev account and Dribbble are ready: account, credits and Dribbble 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": "dribbble_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 burden. It discloses what is inspected (account state, credits, Dribbble connection), which implies a non-mutating read, but it never states that it is read-only, whether it requires an authenticated Cotlet.dev session, whether checking consumes credits, or how failure is signalled.

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?

One sentence, verb first, with the three checked components enumerated after a colon — no filler. Minor deduction for "Cotlet.dev account and Dribbble are ready", which reads slightly awkwardly and buries the three checks inside a compound clause.

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?

For a simple zero-parameter tool this covers the essentials, and the enumerated items implicitly sketch the response shape despite there being no output schema. It is still missing the outcome semantics an agent needs — whether an unconnected Dribbble or zero credits produces an error or a reportable status.

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; the baseline for a parameterless tool applies. The colon-separated list of checked items is the only semantic content needed 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?

"Check" plus three named targets (account, credits, Dribbble connection) gives a concrete verb and resource, and it is clearly distinguishable from the sibling action tools (open, click, type, read, close) which manipulate a page rather than report readiness. It stops short of 5 because "ready" is left undefined — the agent cannot tell what a negative result looks like.

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?

Usage is only implied: the readiness framing suggests a pre-flight gate before dribbble_open or the other action tools, but the description never states that, nor does it name any sibling or say when the check is unnecessary. An agent must infer the call ordering itself.

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