Skip to main content
Glama
ServiceBox MCP Server

ServiceBox MCP Server

servicebox_status

Checks Cotlet.dev account and ServiceBox readiness by verifying account status, credits, and ServiceBox connection before workflows run.

Instructions

Check that your Cotlet.dev account and ServiceBox are ready: account, credits and ServiceBox 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": "servicebox_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 must carry the behavioral burden; 'Check' implies a read-only, side-effect-free operation and it enumerates the three things verified. It stops short of saying what happens when a check fails or whether it is cheap/rate-limited, so the disclosure is partial rather than complete.

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 a colon-delimited list of the three checked items — no filler. The preamble 'Check that your Cotlet.dev account and ServiceBox are ready' slightly restates what the list then spells out, but the redundancy is minor.

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 zero-parameter tool with no output schema, the description should indicate what the response conveys (readiness booleans, error details, partial failures). It names the three domains checked, which is helpful, but leaves the shape and meaning of the result undescribed.

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; baseline 4 applies. The description correctly implies the tool operates on the caller's own account/connection rather than on arbitrary IDs.

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 uses a specific verb ('Check') plus a concrete scope: Cotlet.dev account readiness, credit balance, and ServiceBox connection. This clearly separates it from the action-oriented siblings (servicebox_click, servicebox_open, servicebox_type), though it never names a sibling or explicitly contrasts itself with them.

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 ... are ready' implies a preflight/verification use, which is the natural reading for a status tool. However, it gives no explicit when-to-use or when-not-to-use guidance and does not say whether it should be called before every ServiceBox action.

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