Skip to main content
Glama

eventbrite_status

Check readiness of your Cotlet.dev account, credits, and Eventbrite connection before running event workflows. Use it to confirm setup and prevent workflow interruptions.

Instructions

Check that your Cotlet.dev account and Eventbrite are ready: account, credits and Eventbrite 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": "eventbrite_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 burden. It discloses the three things inspected (account, credits, Eventbrite connection) but not that the check is non-mutating, whether it requires authentication, or what a failed verdict looks like. Adequate signal, notable gaps.

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 no padding. Minor redundancy in listing "account" both in the subject and again in the colon-separated breakdown, which slightly muddies rather than wastes space.

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?

With no output schema and no annotations, the description is the only source of information about results, and it only names the checks without describing the response shape or failure reporting. For a simple diagnostic this is close to sufficient, but an agent cannot predict what it will receive.

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; the baseline for a parameterless tool applies. The description correctly presents the tool as taking no input.

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?

States a specific verb ("Check") and enumerates the resources verified: account, credits, and Eventbrite connection. This reads clearly as a readiness/diagnostic tool, plainly distinct from the browser-action siblings (click, open, read, type), though the description never explicitly frames that contrast.

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 "are ready" implies this should be run before attempting Eventbrite operations, but no explicit when-to-use, when-not-to-use, or prerequisite ordering is stated. Usage is inferable rather than directed.

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