Help by DeltaBreen

check_ticket_pages

Read-only

See what a ticket pages layout would be saved as, without saving: the cleaned HTML and CSS, and what was removed. A refusal says which part is missing or where a part must go. Use it before save_ticket_pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>",
      "html": "<html>"
    },
    "name": "check_ticket_pages"
  }
}

Input Schema

Name	Required	Description
`css`	No	The layout's CSS. It applies inside the layout only. No @import and no backslashes.
`html`	Yes	The layout's HTML: a data-help="list" part holding one data-help="row", and a data-help="ticket" part holding data-help="messages" (with one data-help="mine" and one data-help="theirs", each holding a data-help="text"), a <textarea data-help="reply"> and a <button data-help="send">. get_ticket_pages lists every part. Scripts, images, inline styles and handlers are removed.
`product_id`	Yes	The site's id (a uuid), from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- changedInput schema / properties / css / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
First observedOct 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond readOnlyHint by describing what the call returns (the cleaned HTML and CSS, and what was removed) and how failures behave (a refusal identifies the missing part or its required placement). The no-write guarantee is stated in the description rather than left to annotations.

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, front-loaded with the preview semantics and ending with the routing instruction. No filler or restatement of the tool name.

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

Completeness5/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 carries the return-value burden and does so: it names the payload (cleaned HTML/CSS, removed items) and the error shape (which part is missing or misplaced). Combined with the fully documented schema, an agent has everything needed to call it correctly.

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 the html/css/product_id descriptions already document syntax, restrictions and the required part structure. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource: a dry-run preview of what a ticket pages layout would be saved as, plus what it returns (cleaned HTML/CSS, removed content). It is clearly distinct from save_ticket_pages (which persists) and get_ticket_pages (which lists parts).

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?

"Use it before save_ticket_pages" gives an explicit ordering and names the sibling it precedes. There are no when-not conditions, but the routing decision for a preview tool is essentially unambiguous.

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

All Help by DeltaBreen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?