Skip to main content
Glama

Ticket attach demo

ticket_attach_demo
Destructive

Attach a demo environment to a ticket so reviewers and humans can see the fix running before approving it. Either pass workspace_id to attach an existing demo, or pass application_id + pr_number + image_tag to deploy a fresh throwaway PR demo (same isolated, TTL-limited lifecycle as deploy_pr_demo) and attach it. The ticket then shows the preview URL and build state.

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

Input Schema

NameRequiredDescriptionDefault
image_tagNoThe container image tag the PR build pushed (deploy path).
pr_numberNoThe pull-request number (deploy path).
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
workspace_idNoAn existing demo workspace to attach. When given, no new demo is deployed.
ticket_numberNoThe per-organisation ticket number.
application_idNoThe Application to deploy a PR demo of (deploy path).
container_portNoThe port the container listens on (defaults to the application's Dockerfile EXPOSE port, or 8080 when none is declared).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, so the safety profile is already carried; the description still adds real value by disclosing the isolated, TTL-limited, throwaway lifecycle of the deployed demo and the side effect that the ticket gains a preview URL and build state. It stops short of stating auth requirements, failure behavior, or whether re-attaching the same ticket replaces an existing attachment.

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 sentences, zero filler, with the outcome stated first and the two invocation paths laid out after. Every clause carries either routing information or behavioral context.

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 7-parameter, no-output-schema tool, this covers purpose, both invocation paths, lifecycle, and the resulting ticket state. The remaining gap is that it doesn't say whether the operation is repeatable or what happens to an already-attached demo when a new one is deployed.

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%, so each parameter is already documented individually, and the baseline is 3. The description does add a cross-parameter constraint the schema cannot express — the either/or grouping of workspace_id versus the application_id + pr_number + image_tag triple — which is genuinely useful but is the only semantic addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ("Attach a demo environment to a ticket") and immediately names the two operating modes. It also names the sibling it mirrors (deploy_pr_demo), so an agent can distinguish this from a plain deploy tool without opening either schema.

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?

It clearly states the two selection paths: pass workspace_id to attach an existing demo, or pass application_id + pr_number + image_tag to deploy a fresh one. What's missing is an explicit exclusion clause — it never says when to call deploy_pr_demo or demo_stop instead of this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.