Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Add a restricted zone

add_zone

Creates a restricted zone: a box of your own room where only you, or you and one person you name (keep_for), may build, paint, or place, move and remove things. Use it to protect what you build. Only a room's owner makes zones. Zones may overlap (then only someone each lets in may build there), last with the room and show in look. Change one with edit_object, lift it with remove_object. Costs one edit.

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>"
    },
    "name": "add_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA few words to know the zone by in look ("zone" by default)
rowsYes[from, to], or [one]
layersYes[from, to], or [one]
columnsYes[from, to], or [one]
keep_forNoThe one person, by name, who may build in the zone besides you; "*" (the default) for you alone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / keep_for / description
      Added value: +"The one person, by name, who may build in the zone besides you; \"*\" (the default) for you alone"
    • addedInput schema / properties / name / description
      Added value: +"A few words to know the zone by in look (\"zone\" by default)"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations establish this is a non-read-only but non-destructive creation. The description adds substantial behavioral context beyond annotations: owner-only creation, access control via keep_for, overlap semantics, zone lifetime, visibility in look, and interaction with edit_object/remove_object. It does not contradict the 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?

The description is front-loaded with the core action and scope, then adds only useful operational details. Despite being a single dense paragraph, every sentence carries relevant information about permissions, lifecycle, alternatives, or cost.

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 five-parameter creation tool with no output schema, the description covers the needed behavioral context: owner restrictions, access semantics, overlap behavior, lifetime, visibility, and related edit/remove operations. Parameter details not repeated here are fully covered by the schema.

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 100%, so the schema already documents all five parameters. The description adds meaning by explaining that keep_for grants access to one named person besides the owner and that zones show in look, but it does not elaborate on the rows/columns/layers coordinate arrays beyond the schema's own descriptions.

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 states a specific verb and resource: it creates a restricted zone in a room. It clearly distinguishes the operation from editing and deleting by naming edit_object and remove_object as alternatives for later actions. It also explains the zone's core purpose, protecting what the user builds.

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

Usage Guidelines5/5

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

The description gives explicit usage context: use it to protect what you build, only a room owner may create zones, zones may overlap, and they last with the room. It also routes the agent to edit_object for changes and remove_object for removal, and notes the edit cost. These details make the when-to-use and alternative behavior clear.

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