Skip to main content
Glama

billetto_open

Open a Billetto page in your signed-in Cloud Browser to manage events, orders, and attendees, with the default page set to https://billetto.com.

Instructions

Open a Billetto page in your signed-in Cloud Browser (default https://billetto.com) to work with manage events, orders and attendees.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://billetto.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the page opens in a signed-in Cloud Browser and gives the default URL, but does not explain navigation behavior, side effects, authentication requirements, error handling, or what happens after opening.

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 wasted preamble. The phrase 'work with manage events' is grammatically awkward, but the overall structure remains concise and readable.

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 simple one-parameter navigation tool with no output schema, the description covers the core action and environment. It still omits behavioral details that would help an agent know what to expect after the page is opened.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single optional URL parameter, so the schema already documents the parameter and its default. The description repeats the default URL but adds no additional meaning about accepted formats or behavior.

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 names a specific verb and resource: opening a Billetto page in the signed-in Cloud Browser, with a default URL. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as billetto_read or billetto_status.

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 'to work with manage events, orders and attendees' implies the tool is used to navigate to a Billetto page before other interactions. However, it gives no explicit when-to-use guidance, prerequisites, or alternatives versus sibling tools.

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