Skip to main content
Glama
l33tdawg

(S)AGE

by l33tdawg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

sage_gov_propose

Submit a governance proposal to modify validator-set operations or execute app-v20 scope actions, with a human-readable justification. Requires admin role.

Instructions

Submit a governance proposal. Validator-set operations use scalar fields; app-v20 scope_action accepts a guided scope object that the node encodes canonically. Requires admin role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoGuided app-v20 scope_action template; the node sorts it canonically and owns the execution heights
reasonYesHuman-readable justification for the proposal
payloadNoOptional legacy base64 operation payload; mutually exclusive with scope
operationYesGovernance operation
target_idNoValidator ID for validator ops; optional for scope_action when scope.scope_id is supplied
target_powerNoVoting power (required for add_validator and update_power)
target_pubkeyNoHex-encoded Ed25519 public key (required for add_validator)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv11.13.9
  2. Removedv11.13.8
  3. Changed6 schema fields changedv11.9.2
    • changedInput schema / properties / operation / description
      Previous value: -"Governance operation; sync_group_action attests one exact federation journal digest"New value: +"Governance operation"
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "add_validator",
-  "remove_validator",
-  "update_power",
-  "sync_group_action"
-]New value: +[
+  "add_validator",
+  "remove_validator",
+  "update_power",
+  "sync_group_action",
+  "scope_action"
+]
    • addedInput schema / properties / payload
      Added value: +{
+  "description": "Optional legacy base64 operation payload; mutually exclusive with scope",
+  "type": "string"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Guided app-v20 scope_action template; the node sorts it canonically and owns the execution heights",
+  "properties": {
+    "controller_validator_id": {
+      "type": "string"
+    },
+    "domains": {
+      "items": {
+        "type": "string"
+      },
+      "minItems": 1,
+      "type": "array"
+    },
+    "members": {
+      "items": {
+        "properties": {
+          "active": {
+            "default": true,
+            "type": "boolean"
+          },
+          "assigned_weight": {
+            "minimum": 1,
+            "type": "integer"
+          },
+          "joined_revision": {
+            "description": "May be omitted only for revision 1",
+            "minimum": 1,
+            "type": "integer"
+          },
+          "validator_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "validator_id",
+          "assigned_weight"
+        ],
+        "type": "object"
+      },
+      "minItems": 1,
+      "type": "array"
+    },
+    "revision": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "scope_id": {
+      "type": "string"
+    },
+    "state": {
+      "enum": [
+        "active",
+        "paused",
+        "retired"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "scope_id",
+    "revision",
+    "state",
+    "controller_validator_id",
+    "domains",
+    "members"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / target_id / description
      Previous value: -"Hex-encoded agent/validator ID"New value: +"Validator ID for validator ops; optional for scope_action when scope.scope_id is supplied"
    • changedInput schema / required
      Previous value: -[
-  "operation",
-  "target_id",
-  "reason"
-]New value: +[
+  "operation",
+  "reason"
+]
  4. Changed2 schema fields changedv11.8.0
    • changedInput schema / properties / operation / description
      Previous value: -"Type of validator change"New value: +"Governance operation; sync_group_action attests one exact federation journal digest"
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "add_validator",
-  "remove_validator",
-  "update_power"
-]New value: +[
+  "add_validator",
+  "remove_validator",
+  "update_power",
+  "sync_group_action"
+]
  5. Addedv8.1.0
  6. Removedv8.0.0
  7. Addedv7.6.1
  8. Removedv7.5.9
  9. Addedv6.6.9

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It discloses the admin role requirement but does not describe side effects, irreversibility, fees, or failure modes. For a mutation tool that submits proposals, more behavioral context is expected.

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?

The description is three sentences with no unnecessary words. It front-loads the purpose, then explains operation distinctions, and ends with the prerequisite. Every sentence adds value, making it highly concise.

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

Completeness3/5

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

Given the tool has 7 parameters, nested objects, no output schema, and no annotations, the description covers the basics but lacks details on proposal lifecycle, scope object structure (beyond 'guided'), and post-submission behavior. It is adequate but not comprehensive.

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%, so baseline is 3. The description adds value by explaining that validator-set operations use scalar fields and scope_action uses a guided scope object, which helps agents understand parameter usage beyond what the schema provides. This justifies a score of 4.

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 clearly states 'Submit a governance proposal.' It distinguishes between two operation families (validator-set ops with scalar fields, scope_action with guided scope object) and mentions the admin role requirement, which is specific and helps differentiate from sibling tools like sage_gov_vote.

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?

The description provides implicit guidance by differentiating operation types and stating the admin role prerequisite, but it lacks explicit when-to-use or when-not-to-use instructions relative to alternatives. No exclusions or comparisons to sibling tools are given.

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