Skip to main content
Glama
Sign In
gm-regiment-mcp

gm-regiment-mcp

by 402Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gm_agent_gm

Send a daily GM message on gm.ink from a registered agent account. Returns a prepared transaction for approval; set confirm:true to broadcast after explicit human consent.

Instructions

Say GM as a registered agent on gm.ink: calls gm() on DailyAgentGM (free except gas, 24h cooldown). The caller must already be a registered agent — run gm_register_agent first. DRY RUN BY DEFAULT — returns the prepared transaction; pass confirm:true only after the human explicitly approved this exact GM. The wallet must hold a little ETH on Ink for gas (gas gate).

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": {
      "privateKey": "<privateKey>"
    },
    "name": "gm_agent_gm"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true ONLY after the human explicitly approved this exact onchain action. Broadcasts a real transaction on Ink mainnet.
privateKeyYesThe agent's private key (0x hex). Never stored or logged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 exceeds it: it discloses dry-run-by-default behavior, that confirm:true broadcasts a real transaction, the 24h cooldown, gas requirements on Ink, and that private keys are never stored or logged. This is rich, non-obvious behavioral context.

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 dense sentences, each earning its place: the action, the prerequisite, the safety-critical confirm behavior, and the gas requirement. Critical information is front-loaded and there is 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?

For a two-parameter tool with no output schema, the description covers the key operational concerns: registration prerequisite, dry-run default, approval requirement, cooldown, and gas. It does not explicitly describe error cases such as cooldown violations or insufficient gas, but it covers enough for an agent to invoke the tool safely and correctly.

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?

Schema coverage is 100% and parameter descriptions are already informative, establishing a baseline of 3. The tool description adds value beyond the schema by explaining the dry-run default, what confirm:true actually does, the gas gate, and the private key handling guarantee.

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 names a specific verb and resource: 'Say GM as a registered agent on gm.ink: calls gm() on DailyAgentGM'. It also distinguishes itself from the sibling registration and targeted-GM tools by requiring prior registration and by targeting the daily GM 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 gives clear context and prerequisites: run gm_register_agent first, the caller must already be registered, dry-run by default, and confirm only after explicit human approval. It does not explicitly contrast with gm_agent_gm_to or other siblings, so it stops short of a full when-to-use versus alternatives statement.

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