Skip to main content
Glama
michaeljfazio

cardano-node-mcp

by michaeljfazio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Constitution Action

cardano_governance_action_create_constitution
Idempotent

Create a new constitution governance action on Cardano by providing anchor and constitution details. Generates the action for submission to the blockchain.

Instructions

Create a new constitution governance action.

Args:

  • anchor_url (string): Anchor URL

  • anchor_data_hash (string): Anchor data hash

  • deposit (number): Deposit in lovelace

  • return_addr (string): Stake address for deposit return

  • constitution_url (string): Constitution document URL

  • constitution_hash (string): Constitution document hash

  • constitution_script_hash (string, optional): Guardian script hash

  • prev_governance_action_tx_id (string, optional): Previous action tx ID

  • prev_governance_action_index (number, optional): Previous action index

  • out_file (string): Output path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depositYesDeposit in lovelace
out_fileYesOutput path
anchor_urlYesAnchor URL
return_addrYesStake address for deposit return
anchor_data_hashYesAnchor data hash
constitution_urlYesConstitution document URL
constitution_hashYesConstitution document hash
constitution_script_hashNoGuardian script hash
prev_governance_action_indexNoPrevious action index
prev_governance_action_tx_idNoPrevious action tx ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false, telling the agent this is a non-destructive write. The description adds no behavioral context such as deposit handling, whether the action needs to be submitted separately, or what out_file produces. It merely restates parameters, so it fails to add value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence followed by a bulleted list of parameters that repeat the schema. The parameter list is redundant and adds no new information, making the description longer than necessary without improving clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a governance action creation tool with 10 parameters, no output schema, and no usage context, the description is incomplete. It omits how the returned transaction should be used (e.g., signing/submission), deposit return mechanics beyond the parameter name, and any relation to sibling query tools like cardano_query_constitution.

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 description coverage is 100%, so the schema fully documents all ten parameters. The description's args list duplicates the schema descriptions verbatim (e.g., 'Deposit in lovelace', 'Anchor URL') without adding syntax, format, or constraint details. Baseline 3 is appropriate when the schema does all the work.

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 ('Create a new constitution governance action'), distinguishing it from sibling tools like cardano_governance_action_create_info or _create_hard_fork. The purpose is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., needing a signed transaction, deposit requirements, or governance context). The description only lists parameters, leaving invocation conditions to inference.

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