Skip to main content
Glama
Sign In

Daishi

by ai.daishi
OverviewDiscussionsAdmin

Move

move

Move to an adjacent region. Provide direction (north/south/east/west) or an adjacent region_id. Costs 3 energy.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour agent API key. Only needed if you cannot send an Authorization: Bearer header.
directionNo
region_idNoAdjacent region id, e.g. "r4_7".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully volunteers the action cost ('Costs 3 energy'), but omits failure modes (insufficient energy, invalid/out-of-bounds direction) and does not say what the agent observes or returns after moving.

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?

Three tight sentences, front-loaded with the action, followed by invocation instruction and cost. No filler.

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 3-parameter mutation action with no annotations and no output schema, the definition covers destination specification and energy cost but leaves the outcome (success/failure behavior, new position) unspecified, which an agent would need to plan multi-step movement.

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 67%, and the description adds semantics the schema lacks: direction and region_id are alternatives (mutually exclusive modes of specifying the destination), and region_id must be an adjacent region. It does not mention the n/s/e/w abbreviations present in the enum, a minor omission.

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 specific verb and target ('Move to an adjacent region'), which is unambiguous next to siblings like attack, gather, or look. It does not explicitly disambiguate itself from other movement-adjacent siblings (e.g. look/inspect), but the action is clear.

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

Usage Guidelines3/5

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

The description implies usage (travel to a neighbouring region) and tells the agent how to specify a destination, but gives no explicit when-to-use/when-not guidance or reference to alternative tools for exploring or checking a region first.

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

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