Skip to main content
Glama

skiddle_guide

Find out how to navigate Skiddle Promotion Centre screens and sign in, then manage promoter events, tickets, orders, guestlists, and discount codes. Call it first for Skiddle tasks.

Instructions

How to work in Skiddle (manage promoter events, tickets, orders, guestlists and discount codes): 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": "skiddle_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 implies a read-only reference by describing the content as screens and a sign-in link, and the sequencing hint is useful context, but it never states that the tool performs no mutations, whether the guidance is static or generated, or how the caller's task influences the response. Adequate but leaves real behavioral questions open.

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?

Two short sentences, front-loaded with the tool's identity and followed by the critical "call this first" directive. The parenthetical domain list is dense but earns its place by scoping what the guide covers. Minimal waste overall.

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, the description must convey what comes back, and it only gestures at that ("screens and the sign-in link"). It omits whether the response is instructional text, navigation references, or links, and whether it is tailored by the task argument. Sufficient to select the tool, not sufficient to predict its output.

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?

The tool has one parameter at 100% schema description coverage ("What you want done in Skiddle, in your words"), so the schema already defines it. The description does not explain how the task string shapes the returned guidance — whether it filters topics or is simply echoed — so it adds no meaning beyond the schema. Baseline 3 applies.

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 resource (a guide to working in Skiddle) and enumerates the domains it covers — promoter events, tickets, orders, guestlists, discount codes, screens, and the sign-in link. That is enough to distinguish it from the action-oriented siblings (click/close/open/read/status/type). It stops short of saying what form the guide takes (text instructions vs. URLs), which keeps it off a 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" is an explicit sequencing instruction that tells the agent when to reach for this tool relative to everything else. There are no when-not conditions or named alternatives, but for an orientation tool the primary guidance need — ordering — is stated directly.

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