Skip to main content
Glama

投饵机开关

tool_79a28b99
Read-onlyIdempotent

控制养殖场投饵机。switchOn=true 开启投饵并投料,false 关闭;开启时用 weight 指定投饵重量。

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": {
      "weight": "<weight>",
      "switchOn": "<switchOn>"
    },
    "name": "tool_79a28b99"
  }
}

Input Schema

NameRequiredDescriptionDefault
weightYes投饵重量单位克,仅 switchOn=true 时生效;关闭时该值会被忽略
switchOnYes是否开启投饵机,true 开启,false 关闭

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description describes an action that physically starts a machine and dispenses feed ('开启投饵并投料'), which changes the environment. That is a direct contradiction, and there is no discussion of persistence, reversibility, or failure behavior.

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?

One short paragraph, front-loaded with what is controlled, followed by the on/off semantics. Slightly wasteful only in the final clause, which duplicates schema text about weight applying only when on.

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?

Given only two fully documented parameters and no output schema, the description covers the call mechanics. It is thin on operational reality — no indication of what happens if the feeder is offline, whether the on-state persists, or what is returned — and the read-only claim conflicts with the described physical effect.

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 both parameters are already fully described, including that weight is ignored when switchOn=false. The description restates exactly that, so it neither corrects nor adds meaning beyond the schema; the baseline of 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?

The description names a specific resource (养殖场投饵机) and a concrete operation (turning it on/off with feed dispensing), plus the meaning of switchOn. It is clear and actionable, though it does not need to and does not distinguish itself from any sibling, since no sibling touches irrigation or feeding hardware.

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?

It implicitly tells the agent to set switchOn=true to start feeding and false to stop, which is enough to pick a value. There is no statement of preconditions (device online, current state, confirmation for a physical action) or when-not-to-call guidance, so half of the guidance is left inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.