Geode

Surveys: make a new survey 3

geode_surveys_make_a_new_survey_3

Create a 3-question survey that pays each respondent payout. value must be at least payout × max_responses (the survey's budget). Writes to the chain: this prepares an unsigned transaction (an intent) for signer; nothing happens until you sign it with geode-local-signer and submit it with geode_submit_intent.

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": {
      "signer": "<signer>",
      "survey_name": "<survey_name>",
      "public": "<public>",
      "payout": "<payout>",
      "max_responses": "<max_responses>",
      "question_1": "<question_1>",
      "question_2": "<question_2>",
      "question_3": "<question_3>",
      "value": "<value>"
    },
    "name": "geode_surveys_make_a_new_survey_3"
  }
}

Input Schema

Name	Required	Description
`value`	Yes	GEODE to send with this call (explicit; never inferred)
`payout`	Yes	Amount in GEODE as a decimal string (e.g. "1.25"), or {"raw": "<planck>"}
`public`	Yes
`signer`	Yes	Your account address (SS58). The transaction is prepared for this account; you sign it on your own machine with geode-local-signer.
`question_1`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`question_2`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`question_3`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`survey_name`	Yes	UTF-8 text, at most 512 bytes; no control or invisible characters
`confirm_token`	No	Token from the first call, to confirm this irreversible action
`max_responses`	Yes	Non-negative integer as a string of digits

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag a non-read-only, open-world write. The description adds substantial context beyond them: this only prepares an unsigned intent, nothing is committed until external signing and geode_submit_intent, plus the budget invariant (value >= payout × max_responses). It omits the confirm_token two-step flow that the schema hints at, keeping it short of a 5.

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 tight sentences, front-loaded with the purpose, then the budget constraint, then the intent lifecycle. No filler; each sentence carries information.

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 mutation tool with no output schema, it covers what the action does, the cost invariant, and the required follow-up steps. The unmentioned confirm_token / irreversibility confirmation step is the one gap, though it is documented in the schema.

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 90%, so baseline is 3, and the description earns above baseline by stating the business rule tying value to payout × max_responses and clarifying payout as the per-respondent amount — semantics the schema does not express.

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?

States a specific verb+resource with scope: 'Create a 3-question survey that pays each respondent payout'. The '3-question' qualifier implicitly differentiates it from the make_a_new_survey_1/_5 siblings, though it never names them explicitly.

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?

Explains the completion workflow (sign with geode-local-signer, submit with geode_submit_intent), which is useful downstream context. However it gives no guidance on when to choose this 3-question variant over the 1- or 5-question siblings, leaving the primary selection decision to inference.

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

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