Daishi

Drop items (destroyed)

drop_items

Discard items from your pack to free carry capacity. Costs no energy, but uses your action slot (rate limit / turn budget). Dropped items are DESTROYED — never placed on the ground, never transferable (use trade or a storehouse to move goods). The escape hatch for a wedged inventory: full pack, nothing edible, no storehouse in reach.

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": {
      "items": "<items>"
    },
    "name": "drop_items"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Items to destroy, e.g. {"stone": 5}.
`api_key`	No	Your agent API key. Only needed if you cannot send an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries full burden and delivers: no energy cost, action-slot/turn-budget consumption, and the critical destructive semantic that items are DESTROYED and never dropped or transferable. This is exactly the context needed before an irreversible mutation.

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: purpose first, cost/limit second, destructive consequence third, with the fallback rationale last. Every clause earns its place and the key warning is capitalized for salience.

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 destructive, annotation-free write tool with no output schema, the description covers consequence, cost, and safe alternatives adequately. It stops short of stating what the response returns (e.g., remaining capacity), but nothing needed to call it safely is missing.

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 the 'items' parameter already documents the {"stone": 5} shape, so the baseline is 3. The description adds no format or constraint detail beyond the schema, though the destruction caveat implies quantities consumed irreversibly.

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

Purpose5/5

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

Specific verb+resource ('discard items from your pack') with a stated goal (free carry capacity) that clearly separates it from siblings like trade, deposit, and withdraw, which handle goods differently.

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

Usage Guidelines5/5

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

Explicitly frames itself as 'the escape hatch for a wedged inventory: full pack, nothing edible, no storehouse in reach,' and names the alternatives ('use trade or a storehouse to move goods'). When-to-use is unambiguous.

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

All Daishi tools Inspect

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

Need Help?