Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Unlock shape

unlock_shape

Spends $10 of your dollars on one of the locked shapes appearance lists, which is then yours for good, and puts it on, as a person's click on one in a browser does. A shape you hold already is only put on, for nothing. 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": {
      "part": "<part>",
      "shape": "<shape>"
    },
    "name": "unlock_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYesThe part the shape is for.
shapeYesIts number from appearance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare that this is not read-only and not destructive. The description adds real context the annotations don't: a $10 charge, permanent ownership, an equip side effect, and a cost of one edit. It doesn't say what happens if funds are insufficient or whether the call fails atomically.

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?

It leads with the cost, then covers the free case and the edit cost in three compact sentences. The 'as a person's click on one in a browser does' clause is awkward circumlocution but does convey the equip behavior.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with full schema coverage and no output schema, the description covers what gets spent, what is gained, and the side effects. The main remaining gap is failure behavior on insufficient funds or a non-locked shape.

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 coverage is 100% and both parameters are documented there. The description only adds that the shape number comes from an appearance list and that the part belongs to the shape, which is marginal beyond the schema.

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?

The description states a specific verb and resource: it buys a locked shape from an appearance list and equips it. It also clarifies that owned shapes are merely equipped, which separates the behavior from a plain appearance change, though it never names the sibling tool that does that.

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?

It gives a clear conditional: pay $10 for a locked shape, or equip an already-owned shape for nothing. That effectively tells the agent when this tool is and isn't the right one, but it stops short of explicitly routing the free case to another tool.

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