Skip to main content
Glama

billetto_guide

Get step-by-step guidance on Billetto screens, event, order and attendee management, and the sign-in link; use it before starting a Billetto task.

Instructions

How to work in Billetto (manage events, orders and attendees): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Billetto, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/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 reveals that the tool surfaces screens and a sign-in link and should be invoked before other tools, but never states whether it returns read-only documentation text, whether the task argument changes the output, or that it performs no mutations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with scope and ending with the call-order instruction. Nothing is redundant and every clause contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter orientation tool with no output schema, the description is nearly sufficient: it says what subject matter is covered and when to call it. It leaves a small gap by not indicating the form of the response (textual guidance vs. screen listing) that the agent will receive.

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 coverage is 100% and only one optional parameter ('task') exists, so the schema already explains it fully. The description adds no meaning about how the free-text task influences the returned guidance, making the baseline 3 appropriate.

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 the resource (Billetto) and scopes it to screens, sign-in link, and managing events, orders and attendees, which clearly separates it from action-oriented siblings like billetto_click or billetto_read. The verb is soft ('How to work in...') rather than a concrete action such as 'returns usage guidance', so it falls short of a clean 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives explicit sequencing guidance relative to the sibling tools, telling the agent to orient before acting. It does not state when the tool should be skipped or what to do if guidance is insufficient, so it stops short of full when/when-not coverage.

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