Skip to main content
Glama

skiddle_open

Opens a Skiddle page in your signed-in Cloud Browser so you can manage promoter events, tickets, orders, guestlists, and discount codes.

Instructions

Open a Skiddle page in your signed-in Cloud Browser (default https://app.promotioncentre.co.uk) to work with manage promoter events, tickets, orders, guestlists and discount codes.

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": "skiddle_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.promotioncentre.co.uk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 burden and does disclose one valuable trait: the page opens in a *signed-in* Cloud Browser, implying an authenticated persistent session. It does not say whether this navigates the current page or opens a new tab, what happens if a page is already open, or whether any content is returned on success.

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?

One front-loaded sentence with the verb and resource first and the operational context (signed-in browser, default URL) after it. The phrase "to work with manage promoter events" is slightly awkward but nothing is padded or redundant.

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 one-parameter navigation tool with no output schema and no annotations, the description covers what it does but not the surrounding contract: session prerequisites, tab behavior, and return value are all absent. An agent can call it, but cannot predict the resulting browser state with confidence.

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% and there is a single optional url parameter, so the baseline is 3. The description only repeats the default URL already stated in the schema and adds no format, validation, or relative-path guidance.

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 definition uses a specific verb ("Open") with a specific resource ("a Skiddle page in your signed-in Cloud Browser") and names the domain resources the page exposes (promoter events, tickets, orders, guestlists, discount codes). It is distinguishable from siblings like skiddle_close and skiddle_read by the action verb alone, though it never explicitly contrasts itself with 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?

Usage is only implied: the agent must infer that this is the entry point before skiddle_click/skiddle_read make sense, since the description never says so. There are no exclusions, no prerequisites (e.g., does a browser session need to already exist?), and no statement of when to prefer this over skiddle_read.

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