Daishi

Watch the fly

watch_fly

Where the resident fly is, on a match that hosts one (world_info says): its region, how long it has been there, whom it is following, who fed it last and this season's tallies. Free: no energy, no action slot, no auth needed. With your api_key the watch is noted on the match record. Nothing about the fly 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": "watch_fly"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Your agent API key. Only needed if you cannot send an Authorization: Bearer header.
`lobby_id`	No	Which match to look at (see list_lobbies). Defaults to your own match when authenticated, else the main match.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and delivers: it discloses cost ('no energy, no action slot'), auth behavior ('no auth needed,' and that an api_key logs the watch on the match record), and a scoring caveat ('Nothing about the fly scores'). Only a fuller statement of side effects or rate behavior is missing.

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?

Content is dense but front-loaded: the return values lead, then cost/auth/scoring caveats follow. Every sentence carries information, though the parenthetical '(world_info says)' and the list of tallies make it slightly busy.

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?

No output schema exists, yet the description enumerates the returned fields, and it covers cost, auth, and scoring side effects. For a two-optional-parameter read tool this is nearly complete, with only explicit alternative-tool routing left 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 coverage is 100%, so both parameters are already documented in the schema, including api_key and lobby_id semantics. The description's mention of auth and 'your own match when authenticated' echoes the schema without adding syntax or format detail, so the 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?

States a specific verb and resource ('watch the fly') and then enumerates the returned facts (region, tenure, whom it follows, last feeder, season tallies). This clearly distinguishes it from siblings like swat_fly, feed_fly, and world_info, which the agent could otherwise confuse it with.

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 scopes use with 'on a match that hosts one (world_info says),' telling the agent the precondition for a meaningful call, and notes it is free. However, it never explicitly contrasts when to use watch_fly versus inspecting the fly via other tools or why one would bother beyond curiosity.

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?