agent-passport-system-mcp

Propose Charter Amendment

propose_amendment

Propose an amendment to a charter by supplying a full replacement CharterCore, not a patch, and generate the proposer signature.

Instructions

Propose an amendment to a charter. Supplies a full replacement CharterCore, not a patch. The SDK derives the signing preimage and produces the proposer signature. Session state is not an authoritative registry: amendments live only in this process, are lost on restart, and carry no external trust.

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": {
      "charter_id": "<charter_id>",
      "proposed_charter": "<proposed_charter>",
      "description": "<description>",
      "proposer_private_key": "<proposer_private_key>",
      "proposer_public_key": "<proposer_public_key>"
    },
    "name": "propose_amendment"
  }
}

Input Schema

Name	Required	Description
`charter_id`	Yes	Charter being amended
`description`	Yes	Human-readable description of the change
`effective_at`	No	ISO 8601, when the amendment takes effect if approved
`proposed_charter`	Yes	Full CharterCore replacement, not a patch
`proposer_public_key`	Yes
`proposer_private_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv5.0.0Aug 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, idempotent=false, destructive=false), and the description goes well beyond them by disclosing that session state is non-authoritative, that amendments are lost on restart, and that they carry no external trust. It also explains the SDK derives the signing preimage and produces the signature. Missing only the permission/auth requirements and the post-proposal lifecycle.

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?

Three tight sentences with the core action and replacement-semantics caveat front-loaded, followed by the trust/ephemerality note. 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 mutation tool with annotations present and no output schema, the description adequately covers ephemerality, trust posture, and replacement semantics. It leaves open what the proposal returns and whether approval is required, which are minor gaps given the annotation coverage.

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 67%, so several params (proposer_public_key, proposer_private_key, effective_at) lack descriptions. The description reinforces 'full replacement, not a patch' for proposed_charter (already in the schema) and implies the private key drives signing, but adds little new per-parameter meaning, so the baseline 3 holds.

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 ('Propose') and resource ('an amendment to a charter'), and adds that it supplies a full CharterCore replacement rather than a patch. It does not explicitly name the adjacent siblings (sign_amendment, verify_amendment, create_charter), so differentiation must be inferred from 'produces the proposer signature'.

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 versus sign_amendment, verify_amendment, or create_charter, and no stated prerequisites for a multi-signature approval flow. The description explains what happens internally but not when an agent should choose this tool.

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

Deploy Server