CoinFactory

Get comment signing message

get_comment_signing_message

Read-onlyIdempotent

Step 1 of posting a comment on a launched token: returns the exact text the author wallet must sign (EIP-191 personal_sign) plus the timestamp it embeds. Then call post_token_comment with the signature.

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": {
      "token": "<token>",
      "body": "<body>",
      "author": "<author>"
    },
    "name": "get_comment_signing_message"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	The comment text
`token`	Yes	Launched token: 'base:0x…' or the 0x address
`author`	Yes	Wallet address that will sign
`replyTo`	No	Comment id to reply to

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds real value beyond them: the returned value is a signing payload bound to a timestamp, and the signing scheme is EIP-191 personal_sign. It does not describe the response shape (field names, whether a nonce/expiry is included), which matters since there is no output schema.

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?

Two sentences, no filler, with the purpose and the required follow-up action front-loaded. Every clause carries information the agent needs to sequence the call.

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 read-only preparation step with no output schema, the description covers the workflow and the nature of the return value (signable text + embedded timestamp). Minor gap: it does not state the response's structure or whether the message expires, which an agent passing the result forward might want.

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 all four parameters including replyTo and format constraints are already documented. The description only implies that body/author/token feed the message construction and adds no format or constraint detail beyond the schema; baseline 3 is appropriate.

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 — returns the exact text the author wallet must sign for a token comment — plus the signing standard (EIP-191 personal_sign) and the embedded timestamp. It is clearly distinguishable from the sibling post_token_comment, which is the write half of the flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames itself as 'Step 1 of posting a comment' and tells the agent the next action: 'Then call post_token_comment with the signature.' The alternative/sequel is named with its trigger, so the ordering is unambiguous.

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

All CoinFactory 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?