Skip to main content
Glama

accelo_status

Checks your Cotlet.dev account, available credits, and Accelo connection so you can confirm the integration is ready before running Accelo actions.

Instructions

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real value by enumerating what is inspected (account, credits, Accelo connection), which tells the agent what preconditions are verified. It does not state that the call is read-only/non-mutating or how failures are reported (error vs. a not-ready status), leaving key behavioral traits unspecified.

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 short sentence with the action front-loaded and no filler. The trailing colon list is slightly compressed but still parses cleanly, and nothing is redundant.

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?

This is a low-complexity, parameterless tool, so the description covers the essentials of what is checked. However, with no output schema and no annotations, an agent still cannot tell what the response looks like or whether a failed check surfaces as an error or as data, which is the one thing this description should have closed.

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 no parameters and the schema is an empty closed object at 100% coverage, so there is no parameter meaning for the description to add. Baseline of 4 applies for a zero-parameter tool.

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 specific verb ('Check') and a concrete resource set (account, credits, Accelo connection), so the tool's identity as a readiness/health check is unambiguous. It does not name or contrast any sibling, but the sibling names (click, close, open, read, type) are all action tools, so the status check is naturally distinguishable.

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 word 'ready' implies this is a pre-flight or precondition check, which hints at when to call it, but the description never states when to use it, when not to, or what to do if the check reports a problem. Usage must be inferred from the framing rather than read directly.

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