Skip to main content
Glama
agent-passport-system

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Promote Provisional Statement

aps_promote_statement
Read-onlyIdempotent

Promote a provisional statement to binding by attaching a PromotionEvent that satisfies the required m-of-n principal signatures in the promotion policy.

Instructions

Commitment boundary: promote a provisional statement to binding by attaching a PromotionEvent that satisfies the PromotionPolicy (m-of-n principal signatures). dead_man_elapsed cannot promote, because the dead-man path auto-withdraws the statement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policyYesPromotionPolicy {id, required_signers, threshold, max_time_to_promote}
statementYesProvisionalStatement from aps_create_provisional
promotion_eventYesPromotionEvent with kind, promoted_at, promoter, promoter_signature, policy_reference

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
+  "statement",
+  "promotion_event",
+  "policy"
+]
  2. Addedv2.8.0

TDQS

B3/5.0
Behavior1/5

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

The description clearly describes a state-changing operation ('promote ... to binding by attaching a PromotionEvent'), yet annotations declare readOnlyHint=true. This is a direct contradiction: the tool mutates state while structured metadata claims it is read-only. Annotation Contradiction flagged.

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?

Two sentences, front-loaded with the 'Commitment boundary' framing, with the critical caveat about dead_man_elapsed placed immediately after the core action. No filler.

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?

Covers the core mechanism and one important exclusion, which is reasonable for a 3-param tool with no output schema. But the safety profile is actively misleading (readOnlyHint=true on a mutation), and the description does nothing to correct it, leaving the agent with a wrong mental model of side effects.

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 already documents statement, promotion_event and policy. The description adds the constraint that the PromotionEvent must satisfy the PromotionPolicy (m-of-n principal signatures), which adds semantic value beyond the schema, so baseline 3 is appropriate.

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 and resource ('promote a provisional statement to binding') and names the mechanism (attaching a PromotionEvent satisfying a PromotionPolicy). An agent can distinguish this from aps_withdraw_provisional and aps_verify_promotion, though the description doesn't explicitly name those siblings.

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?

Provides one useful exclusion ('dead_man_elapsed cannot promote, because the dead-man path auto-withdraws the statement'), which is real routing guidance. However, it gives no explicit when-to-use context relative to aps_verify_promotion or the conditions under which a promotion should be attempted.

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