Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Look at blocks

look_blocks
Read-only

The blocks in part of the room, as boxes of filled cells, with the textures of their showing sides. Rows, columns or layers left out are those around you (all layers).

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

Input Schema

NameRequiredDescriptionDefault
rowsNo[from, to], or [one]
layersNo[from, to], or [one]
columnsNo[from, to], or [one]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds useful context about what is returned (boxes of filled cells with visible-side textures) and the default scope, but it does not describe output format, size limits, or coordinate conventions, leaving meaningful behavioral gaps.

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 compact sentences with no filler. The return-shape description is front-loaded and the default-scope rule follows, though the first sentence is grammatically elliptical and slightly harder to parse than necessary.

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?

For a read-only observation tool with three optional parameters and no output schema, the description covers the return concept and parameter defaults. However, it does not clarify the coordinate system, what 'around you' means in range terms, or how to interpret the output, which an agent would need to call it confidently.

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 '[from, to], or [one]' syntax is already documented. The description adds genuinely new meaning by explaining what happens when parameters are omitted: rows and columns default to the area around you, and all layers are included. This omission semantics is not in the schema and is valuable for correct invocation.

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

Purpose3/5

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

The description identifies the resource (blocks in part of the room) and the return concept (boxes of filled cells with textures of showing sides), but it is a sentence fragment with no verb, so the action is only implied by the tool name. It does not differentiate itself from the sibling 'look' tool or explain how it differs from 'textures'.

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?

The only guidance is a default-behavior note: omitted rows/columns/layers default to those around you, with all layers included. There is no explicit statement of when to use this tool versus alternatives like 'look' or 'textures', and no exclusions or prerequisites are given.

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