Skip to main content
Glama
Billdr MCP Server

Billdr MCP Server

billdr_status

Verifies your Cotlet.dev account and Billdr connection are ready by checking account status, available credits, and connection health before you proceed.

Instructions

Check that your Cotlet.dev account and Billdr are ready: account, credits and Billdr 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": "billdr_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 behavioral burden. It discloses what is checked—account, credits, and Billdr connection—but does not state whether the operation is read-only, what permissions are needed, or how readiness failures are represented. For a zero-parameter status tool this is adequate but incomplete.

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?

The definition is a single, front-loaded sentence with no filler. The only slight redundancy is repeating "account" in the readiness list, but it remains clear and efficient.

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?

The tool is simple and the description names the three readiness checks, which is useful context. However, because there is no output schema, the description could better explain what a successful or failed status check returns, leaving a gap for an agent interpreting results.

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 has zero parameters, so there are no parameter semantics to explain and the baseline is 4. The description does not need to compensate for any schema gaps.

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 resources being verified: Cotlet.dev account, credits, and Billdr connection. It is clearly a readiness check rather than an action, which implicitly distinguishes it from sibling tools like billdr_click or billdr_open, though it does not explicitly name 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 phrase "Check that your ... are ready" implies using the tool before performing Billdr actions, but it does not explicitly state when to use it, when not to use it, or which sibling to choose for actual operations. The guidance is therefore implied rather than explicit.

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