Skip to main content
Glama

xTiles

by app.xtiles
OverviewDiscussionsAdmin

xtiles_reset_tile_styles

DestructiveIdempotent

Clear the palette color (color and color_size) of the listed tiles on an xTiles page (view). Structural style (icon) and any custom workspace color are left unchanged — this manages only the palette color. A text page’s tile style is fixed — the call is refused there. Returns the resulting full tile-style state.

Input Schema

NameRequiredDescriptionDefault
viewIdYesView ID of an xTiles page. You can also extract it from a page URL — it is the last path segment, whatever the domain, e.g. `https://xtiles.app/6740858058af8a09bf6096e6` → viewId is `6740858058af8a09bf6096e6`. Discover IDs programmatically via `xtiles_list_projects` or `xtiles_get_project_content`.
tile_idsYesIDs of tiles whose palette color should be cleared (the `tile_id` from xtiles_get_tile_styles).

Output Schema

NameRequiredDescriptionDefault
tilesYes
view_idYes
editableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / editable
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description meaningfully bounds that destruction ('structural style (icon) and any custom workspace color are left unchanged') and discloses a failure mode (text pages are refused). The closing note about the return value is redundant with the existing output schema, but the scope-of-damage disclosure is genuine added value.

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?

Three front-loaded sentences with the destructive action and its limits stated first. The final sentence restates a return value already covered by the output schema, which is the only wasted line.

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?

For a two-parameter tool with full schema coverage, complete annotations, and an output schema, the description covers everything an agent needs: what is cleared, what survives, the refusal case, and the fact that this is idempotent and destructive.

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%, including an example for extracting viewId from a URL and a pointer to xtiles_get_tile_styles for tile_ids. The description adds no format or syntax detail beyond the schema, so the baseline 3 is 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?

States a precise verb ('Clear') and resource ('palette color (`color` and `color_size`) of the listed tiles'), plus the exact boundaries of that resource. It implies the inverse relationship to xtiles_set_tile_styles but never names that sibling, so an agent still has to infer the pairing.

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?

Provides a firm when-not condition — 'A text page's tile style is fixed — the call is refused there' — and implicitly handles the when-to-use case via the reset-vs-set distinction. It does not explicitly name xtiles_set_tile_styles as the alternative for setting rather than clearing.

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

All xTiles toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources