Skip to main content
Glama

extrabat_status

Verify your Cotlet.dev account, credits, and Extrabat connection are ready. Use this check before running customer, quote, or invoice workflows.

Instructions

Check that your Cotlet.dev account and Extrabat are ready: account, credits and Extrabat 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": "extrabat_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 value by enumerating the three things verified (account, credits, Extrabat connection), which tells the agent what state is being probed. However, it never states that the call is read-only, whether it consumes credits, or what a failed check yields, leaving meaningful behavioral gaps with zero annotation coverage.

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 a front-loaded verb and a compact list of the checked facets, containing no filler or repetition. Slight awkwardness comes from the colon list doing double duty as both scope and elaboration. It earns its length but could be marginally tighter.

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, zero-annotation, no-output-schema tool, the description covers what is checked but not how results should be read back. Since no output schema exists, the description would ideally give a hint about the shape or meaning of a readiness result. It is minimally sufficient but leaves the agent guessing about return values and failure semantics.

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, which is the baseline expectation for a no-arg call. Nothing in the description invents or misdescribes inputs. The entry is therefore adequate by default.

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') and names the exact resource being inspected: Cotlet.dev account readiness, credits, and the Extrabat connection. This clearly distinguishes it from the sibling action tools (click, open, type, read), which operate on a page. It stops short of a 5 only because it frames the purpose as a readiness check without saying how the result should be interpreted.

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 word 'ready' suggests calling this before attempting Extrabat actions, but no explicit when-to-use or when-not-to-use statement is given. It names no alternative for troubleshooting a failed check, even though extrabat_guide exists among the siblings. An agent can infer the precondition role but must guess at the ordering.

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