Skip to main content
Glama

billetto_status

Verify Cotlet.dev account readiness, available credits, and Billetto connection status before managing events, orders, or attendees.

Instructions

Check that your Cotlet.dev account and Billetto are ready: account, credits and Billetto 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": "billetto_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full disclosure burden, and it leaves the most important traits unstated: whether the call is read-only and side-effect free, whether it requires authentication first, whether it fails or returns a status when a check is negative, and whether it consumes or reveals credit information. "Check" implies a read, but that is inference rather than disclosure.

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 the intent first and the enumerated checks after the colon — no filler. It is arguably too short for what it needs to convey, but nothing present is wasted.

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?

There is no output schema and no annotations, so the description is the only source of information about this tool — yet it never says what a result looks like (per-check booleans? totals? error text?) or what an agent should do with each outcome. For a diagnostic tool whose entire value is its return value, that is a meaningful gap.

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 add; this sits at the stated baseline. The description does at least clarify that all three checks happen in one call rather than requiring separate arguments.

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 gives a specific verb ("Check") and enumerates the exact resources verified: account, credits, and the Billetto connection. This reads clearly as a readiness/diagnostic probe, which is distinguishable from the sibling tools (click, open, read, type) that manipulate a session.

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 — an agent can infer this should be called before or when troubleshooting other Billetto operations, but the description never states when to call it, when not to, or what to do with a negative result. No alternative or fallback is named.

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