Skip to main content
Glama

ecash_withdraw_arbitrator

Withdraw from the arbitrator role to stop receiving new dispute assignments and end active arbitration participation.

Instructions

Stop being an arbitrator. You won't be selected for new disputes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description must disclose behavioral effects. It states 'You won't be selected for new disputes,' but fails to mention whether existing disputes are affected or if the action is reversible. This is a notable omission for a state-changing tool.

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?

The description is two short sentences, front-loaded, with no unnecessary words. It effectively communicates the core action and a key consequence.

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 simple no-parameter tool, the description covers the primary purpose. However, it omits potential implications for existing disputes, which would be useful for the agent's decision-making. Somewhat incomplete given its simplicity.

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?

The tool has zero parameters, so the description need not add parameter semantics. Per the rubric, the baseline score for no params is 4.

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 clearly states the tool disables arbitrator status with 'Stop being an arbitrator.' It differentiates from the sibling tool ecash_enroll_arbitrator by indicating the opposite action.

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 implicitly conveys when to use it (when the agent no longer wants to arbitrate) but doesn't explicitly mention alternatives or exclusions. The presence of the sibling enroll tool provides context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ecashprotocol/ecash-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server