Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

coinduel_enter_info

Get exact steps to enter Coin Duel: register, pay 0.50 USDC on Base via x402, place a call, and view open rounds. Returns instructions only; no funds spent or call placed.

Instructions

[FREE] Exact steps for an agent to enter Coin Duel today. Returns the register call, the x402 entry endpoint (0.50 USDC on Base, facilitator named in its 402), the call endpoint and the open rounds URL. This tool does not spend money or place a call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it marks the tool [FREE], states plainly that it 'does not spend money or place a call', and discloses the downstream cost (0.50 USDC on Base) and that the facilitator is identified in the 402 response. It stops short of stating the response format or whether the returned endpoints are live-verified.

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?

Three sentences, front-loaded with the [FREE] marker and the safety caveat placed last where it lands hardest. Dense but every clause carries information (cost, chain, 402 facilitator, return contents); no filler.

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?

There is no output schema, and the description compensates by enumerating the four things the caller receives. For a zero-parameter info tool this is close to complete; only pagination/format details and verification status of the returned URLs are left unstated.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not waste words on nonexistent inputs.

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 goal ('exact steps for an agent to enter Coin Duel today') and enumerates exactly what is returned: the register call, the x402 entry endpoint, the call endpoint, and the open rounds URL. It is distinguishable from siblings like coinduel_rules or coinduel_leaderboard by content, though it never names those siblings directly.

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?

Usage is implied by the wording 'steps for an agent to enter Coin Duel today', which tells an agent this is the entry-path reference. However, no explicit when-to-use versus when-not-to-use guidance is given, and the closely related coinduel_rules tool is not referenced as an alternative for rule questions.

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

Deploy Server

Other Tools