Skip to main content
Glama

skiddle_status

Check that your Cotlet.dev account, credits, and Skiddle connection are ready before running Skiddle promotion workflows.

Instructions

Check that your Cotlet.dev account and Skiddle are ready: account, credits and Skiddle 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": "skiddle_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 carries the full behavioral burden. It usefully enumerates the three things verified (account, credits, connection), implying a read-only diagnostic with no state change, but it says nothing about the response shape, failure signaling, or whether checks are billable/live network calls. Adequate but leaving real gaps for an unannotated tool.

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 sentence with the verb front-loaded and no filler; the colon-separated list of checks is efficient. Minor awkwardness in 'Check that your Cotlet.dev account and Skiddle are ready' keeps it from being a model of clarity.

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, no-output-schema health check, the description covers the essential question of what is being verified. The only missing piece is how results are reported, which is a small gap given the tool's simplicity and the enumeration of the three checks.

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 to convey and the baseline of 4 applies. The description correctly omits any argument discussion rather than inventing one.

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?

States a specific verb ('Check') and an explicit scope: account status, credits, and Skiddle connection. This clearly separates it from the sibling action tools (open, click, type, read, close), which manipulate a session rather than report readiness. It stops short of a 5 only because the phrasing 'Check that ... are ready' is a little indirect about it being a status/diagnostics call.

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 implied (verify prerequisites before using the Skiddle automation tools) but never stated. There is no explicit 'call this first', no when-not-to-use, and no mention of what to do if a check fails. An agent can infer the context, which is why it lands at 3 rather than 2.

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