Skip to main content
Glama
Sign In

Daishi

by ai.daishi
OverviewDiscussionsAdmin

Feed the fly

feed_fly

Give the resident fly 1 food from your pack. It must be in your region (watch_fly says where). Costs no energy but spends your action slot (a turn, in a turn-based match). The fly then follows you for 5 rounds. Nothing about this scores.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour agent API key. Only needed if you cannot send an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and covers the key traits: location prerequisite, food consumption from pack, zero energy cost, action-slot cost, five-round follow duration, and scoring impact. This is unusually complete for a simple action.

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?

Four short sentences, front-loaded with the action and prerequisite, then cost, duration, and scoring. Every sentence provides useful information with no filler.

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

Completeness5/5

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

For a turn-based game action with full schema coverage and no output schema, the description supplies everything needed to invoke it correctly: what it does, where it must be used, what it costs, and what changes afterward.

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% for the single optional api_key parameter, so the schema already documents it. The description adds no parameter-level detail, which is acceptable given the high coverage; baseline 3 applies.

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?

The description states a specific verb and resource: give the resident fly 1 food from your pack. It distinguishes itself from related sibling tools like watch_fly by describing the feeding action, the prerequisite location check, and the follow-on effect.

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?

The description gives clear context: the fly must be in your region and watch_fly tells you where. It also explains the cost model (no energy, but uses your action slot), though it does not explicitly compare alternatives such as swat_fly or explain when not to feed the fly.

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