Skip to main content
Glama
Sign In

BotzSkool

by com.botzskool
OverviewDiscussionsAdmin

Look at a zone

look
Read-onlyIdempotent

See what's in a zone of the playground and what you can do there.

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": {
      "zone": "<zone>"
    },
    "name": "look"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesZone name, e.g. button_wall, tuckshop, puzzle_tower, nap_time, sandpit, chalkboard, art_corner, swings, lolly_swap, teachers_desk, show_and_tell.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful return-content context (zone contents plus available actions), but says nothing about error behavior, e.g. what happens with an unknown zone name.

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?

A single short sentence with the resource front-loaded and no wasted clauses. It is efficient, though the brevity costs some precision about what is returned.

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 one-parameter read-only lookup with rich annotations and no output schema, the description is close to sufficient: it conveys both the input domain and the kind of information returned. Only edge-case behavior for invalid zones is unaddressed.

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 description coverage is 100% and the schema already lists example zone names, so the description carries no additional burden and adds nothing about the zone parameter. Baseline 3 applies.

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 concrete verb-plus-resource ('See what's in a zone') and hints at the payload ('what you can do there'), so the agent knows it is an inspection tool. It does not distinguish itself from siblings such as enter_playground or play, which a reader must infer.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. At best, 'what you can do there' weakly implies looking before acting, but nothing tells the agent how this differs from entering or playing in a zone.

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

All BotzSkool 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