Skip to main content
Glama

agent-transaction-control

by network.flint

Update Agent Mandate

update_agent_mandate
Idempotent

Use this tool to update mutable mandate config for an existing FLINT Agent Passport. This updates allowed actions, amount limits, or notes only. It does not reissue the passport and does not re-sign the identity credential. If the passport is claimed, the caller must be authenticated as its owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mandateYesMutable mandate config to update: allowed_actions, max_transaction_amount, notes.
passport_idYesFLINT Agent Passport id, beginning with kya_.
management_tokenNoClaim token required while the Passport is unclaimed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / management_token
      Added value: +{
+  "description": "Claim token required while the Passport is unclaimed.",
+  "maxLength": 128,
+  "minLength": 32,
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds useful behavioral detail beyond annotations: it updates only specific fields, does not reissue the passport, and does not re-sign the identity credential. It also clarifies owner authentication for claimed passports. No contradiction with the annotations.

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 sentences front-load the operation and scope, then cover exclusions and auth requirements. Every sentence earns its place and there is 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?

Covers the critical behavioral aspects: scope of fields, exclusions, and auth requirements. The main missing detail is whether omitted mandate fields are preserved or cleared during a partial update, and there is no mention of return values despite no output schema being provided.

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 the description does not need to repeat parameter details. It does reinforce the mandate field scope and clarifies how management_token relates to the unclaimed/claimed passport state, adding operational meaning beyond the schema.

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 ('update') and resource ('existing FLINT Agent Passport') and narrows to 'mutable mandate config'. It explicitly distinguishes itself from reissue/re-sign operations, making it clear this is not issue_agent_passport.

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

Usage Guidelines4/5

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

Provides clear context for when to use the tool and spells out an important prerequisite: if the passport is claimed, the caller must be authenticated as its owner. It mentions exclusions but does not name alternative sibling tools explicitly.

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

All agent-transaction-control toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct action and resource: manifest creation, scope generation, passport lifecycle, authorization issuance/verification, reputation lookup, transaction scanning, and architecture validation. Overlapping terms like 'issue_agent_passport' and 'issue_authorization_record' are clearly differentiated by their objects and descriptions.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern with clear verbs (create, generate, get, issue, lookup, run, update, validate, verify). Even where verbs are semantically close (issue vs generate), the pattern remains uniform and predictable.

Tool Count5/5

Ten tools is well-scoped for an agent transaction control domain, covering identity, authorization, verification, trust, scanning, and compliance checks without redundancy. Each tool occupies a necessary niche in the workflow.

Completeness4/5

Core lifecycle coverage is strong: passports can be created, read, and updated, authorizations can be scoped, issued, and verified, and reputation/manifests are accessible. Notable minor gaps include no explicit revocation or outcome-submission tool, but agents can still complete the primary transaction flow.

Resources