Skip to main content
Glama
Sign In
Powder Toy MCP

Powder Toy MCP

by alinflorin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

read_instructions

Returns usage docs for every Powder Toy command so you can learn correct CLI-style syntax before using execute.

Instructions

pt read_instructions: READ THIS FIRST, before using execute. Returns usage docs for every pt command.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full burden of behavioral disclosure. "Returns usage docs" implies a read-only, side-effect-free operation, but the description does not state this explicitly or describe the shape or size of the returned documentation (whether the output is long, or what format it uses).

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?

The description is two short sentences with the urgency front-loaded, so no wording is wasted. The only redundancy is the "pt read_instructions:" name prefix, which repeats information the agent already has.

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 zero-parameter documentation tool with no output schema, the description covers the essentials: what it returns and that it must be read first. A note on the return format or expected length would close the remaining small gap.

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?

The tool takes zero parameters and has 100% schema description coverage, so the baseline is 4. The description adds little parameter-level detail, but none is needed for a parameterless tool.

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 names a specific verb and resource: it "Returns usage docs for every pt command." That wording clearly separates it from the sibling tool execute, which performs actions, and the redundant "pt read_instructions:" prefix does not hide this meaning.

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?

"READ THIS FIRST, before using execute" gives explicit ordering guidance and names the alternative (execute). It does not say whether the tool must be called once per session or before every execute invocation, which is the one ambiguity an agent would still face.

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

Deploy Server

Other Tools