Skip to main content
Glama
Sign In
agent-passport-system-mcp

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Get Commerce Spend

get_commerce_spend
Read-onlyIdempotent

Retrieve spend analytics for a commerce delegation to monitor agent spending against the delegation’s allowed spend limit.

Instructions

Get spend analytics for a commerce delegation.

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": {
      "agent_id": "<agent_id>",
      "delegation_id": "<delegation_id>",
      "spend_limit": "<spend_limit>"
    },
    "name": "get_commerce_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent ID
spend_limitYesTotal allowed spend
delegation_idYesCommerce delegation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. Addedv2.8.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing further — not the return shape, not whether spend is scoped to a period or currency, and not why a read tool requires a 'spend_limit' input.

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?

A single short sentence with no filler and the key noun phrase front-loaded. It is efficient, though the brevity edges into under-specification rather than tightness.

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

Completeness2/5

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

With three required parameters and no output schema, the description is the only place to explain what an agent receives and how the unusual required 'spend_limit' input interacts with a read operation. Neither is addressed, leaving a real gap for a tool whose inputs are non-obvious.

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 all three parameters are documented in the schema and the baseline is 3. The description adds no extra meaning, such as whether delegation_id must be an active delegation or whether spend_limit acts as a filter bound versus a validation check.

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?

The description states a specific verb and resource ('Get spend analytics') scoped to a 'commerce delegation', which is clearer than a tautology. However, it does not differentiate itself from adjacent siblings such as generate_settlement or aps_aggregate_settlement, which also deal with commerce/accounting outcomes.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent cannot tell from this text when spend analytics is the right call versus preflight, settlement, or evidence tools.

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