MolTrust MCP Server

mt_shopping_issue_vc

Destructive

Issue a BuyerAgentCredential (W3C Verifiable Credential) for a shopping agent.

Creates a cryptographically signed credential that authorizes an AI agent
to make purchases on behalf of a human, with enforced spend limits.

Args:
    agent_did: DID of the shopping agent (e.g. "did:moltrust:agent123")
    human_did: DID of the authorizing human (e.g. "did:moltrust:human456")
    spend_limit: Maximum spend amount per transaction
    currency: Currency code (e.g. "USDC", "USD")
    categories: Comma-separated allowed categories (e.g. "electronics,books")
    validity_days: Number of days the credential is valid (default 30)

Input Schema

Name	Required	Description
`currency`	Yes	Currency code (e.g. "USDC", "USD")
`agent_did`	Yes	DID of the shopping agent (e.g. "did:moltrust:agent123")
`human_did`	Yes	DID of the authorizing human (e.g. "did:moltrust:human456")
`categories`	Yes	Comma-separated allowed categories (e.g. "electronics,books")
`spend_limit`	Yes	Maximum spend amount per transaction
`validity_days`	No	Number of days the credential is valid (default 30)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedInput schema / properties / agent_did / description

Added value: +"DID of the shopping agent (e.g. \"did:moltrust:agent123\")"

addedInput schema / properties / categories / description

Added value: +"Comma-separated allowed categories (e.g. \"electronics,books\")"

addedInput schema / properties / currency / description

Added value: +"Currency code (e.g. \"USDC\", \"USD\")"

addedInput schema / properties / human_did / description

Added value: +"DID of the authorizing human (e.g. \"did:moltrust:human456\")"

addedInput schema / properties / spend_limit / description
```
Added value: +"Maximum spend amount per transaction"
```

addedInput schema / properties / validity_days / description

Added value: +"Number of days the credential is valid (default 30)"

First observedSep 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=true, and the description adds real context: the output is a cryptographically signed credential with spend limits enforced and a validity window. However, it never explains the destructive/non-idempotent behavior — e.g. whether re-issuing supersedes or duplicates a prior credential, or whether issued credentials can be revoked — which is the main thing an agent would want clarified for a write operation of this kind.

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?

The summary sentence is front-loaded and the second sentence adds substance about signing and spend limits. The Args block is largely duplicated in the schema, so it is mildly redundant rather than harmful.

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?

With 6 parameters, an output schema present and full annotation coverage, the definition is close to sufficient. The remaining gaps are operational rather than structural: no statement about prerequisites, revocation, or what happens to an existing credential when a new one is issued.

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 baseline is 3. The Args section restates the schema descriptions almost verbatim (same examples for DIDs, currency, categories) and adds no extra semantics such as units for spend_limit or supported currency set.

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: 'Issue a BuyerAgentCredential (W3C Verifiable Credential) for a shopping agent', then elaborates that it is a signed credential authorizing agent purchases with enforced spend limits. The shopping-agent framing implicitly separates it from the travel and skill credential siblings, so an agent can pick the right domain tool.

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?

Usage is only implied by the verb 'issue' and the 'on behalf of a human' framing. There is no explicit when-to-use guidance, no mention of the counterpart mt_shopping_verify tool, and no note on prerequisites such as whether the human DID must already be registered before issuing.

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

All MolTrust MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.