Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Paint faces

paint_faces

Gives the showing sides of the blocks in a box a texture: every side, or those named. The room's floor is layer -1's up side, its ceiling layer 16's down side.

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": {
      "rows": "<rows>",
      "columns": "<columns>",
      "layers": "<layers>",
      "texture": "<texture>"
    },
    "name": "paint_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes[from, to], or [one]
sidesNo
layersYes[from, to], or [one]
columnsYes[from, to], or [one]
textureYesA name or number from textures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description must carry the rest. It usefully adds that only *showing* (exposed) faces are painted and that layer -1 up / layer 16 down map to floor and ceiling, but it omits whether existing textures are overwritten and whether ownership or room permissions are required.

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 sentences, front-loaded with the core action and followed by the domain-specific layer mapping. No filler, though the opening clause is grammatically awkward and could be phrased more directly.

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 five parameters, no output schema, and thin annotations, the description covers the region, the sides selection, and the floor/ceiling convention adequately. It still leaves open overwrite behavior and permission requirements for a mutation tool, which an agent would want before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, and the description adds meaning the schema doesn't: 'every side, or those named' clarifies that the optional sides array defaults to all six faces. The floor/ceiling sentence also gives semantic grounding to the -1 and 16 layer bounds, which the schema states only as numeric limits.

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 specific verb and resource: applying a texture to the showing sides of blocks within a box region. The 'showing sides' phrasing and the layer/face mapping make the effect concrete, though it doesn't explicitly contrast with siblings like place_blocks or change_appearance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to reach for this tool versus place_blocks, remove_blocks, face, or change_appearance. The 'every side, or those named' clause describes parameter behavior, not usage context or exclusions.

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

All ThingsPool toolsInspect
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