Skip to main content
Glama
Sign In

prompt-guard-mcp

by io.github.robertoyanguas-ops
OverviewDiscussionsAdmin

get_agent_wallet_status

Read-onlyIdempotent

Inspect an agent's account ledger: remaining free trial calls (out of 5), prepaid USD balance, cumulative spend, total API calls, and total LLM tokens saved. WHEN TO USE: Call before a batch of paid tool executions or after completing a Stripe or USDC top-up to confirm your balance. WHEN NOT TO USE: Do not use to process web content, execute marketplace tools, or submit payments; use the other tools on this server for execution. PARAMETER INTERACTIONS: Omit agent_id to inspect the default trial account derived from your client IP, or pass your explicit agent_id or agd_pass_ session key to check a specific funded wallet. Free and read-only: never charges a fee or consumes a free trial call. Example: get_agent_wallet_status(agent_id='example')

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP.

Output Schema

NameRequiredDescriptionDefault
dataNoStructured tool output payload.
statusYesExecution status ('ok' or 'payment_required').
roi_proofNoToken compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "agent_id": "example"
+  }
+]
  2. Changed6 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • changedInput schema / properties / agent_id / description
      Previous value: -"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."New value: +"Optional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP."
    • addedInput schema / properties / agent_id / maxLength
      Added value: +256
    • addedInput schema / properties / agent_id / minLength
      Added value: +1
    • removedInput schema / properties / tx_hash
      Removed value: -{
-  "description": "Not needed; this tool is free.",
-  "type": "string"
-}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."
    • changedInput schema / properties / tx_hash / description
      Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Not needed; this tool is free."
  4. Changed5 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedInput schema / properties / agent_id / description
      Added value: +"Optional Agent ID or Session Pass (agd_pass_...)"
    • removedInput schema / properties / agent_id / maxLength
      Removed value: -99999
    • removedInput schema / properties / agent_id / minLength
      Removed value: -1
    • addedInput schema / properties / tx_hash
      Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}
  5. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / agent_id / maxLength
      Added value: +99999
    • addedInput schema / properties / agent_id / minLength
      Added value: +1
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it never charges a fee or consumes a free trial call, and the default wallet is derived from the caller's client IP. It does not discuss rate limits or caching, but the cost/free-trial guarantee is meaningful behavioral disclosure.

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?

Front-loaded with the ledger contents, then structured WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS / Example. The labeled sections make it scannable, though the repetition of the read-only guarantee and the worked example add a little bulk.

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

Completeness5/5

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

An output schema exists, so return-value detail is optional, yet the description still names the key fields. With a single optional parameter, no nested objects, and annotations covering safety, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description goes slightly further by naming the agd_pass_ session-key form and framing the two modes as an interaction (omit for IP-derived trial account vs. pass explicit agent_id/session key for a funded wallet), which aids selection even though the schema states the omit behavior.

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 (inspect) and resource (agent's account ledger) and enumerates exactly what is returned: trial calls out of 5, prepaid USD balance, cumulative spend, total API calls, tokens saved. This clearly separates it from the sibling web-content tools (distill_webpage, extract_structured_data, recon_webpage_skeleton), which operate on webpages rather than wallet state.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE (before paid tool batches, after a Stripe or USDC top-up) and WHEN NOT TO USE (not for processing web content, executing marketplace tools, or submitting payments). The exclusion clause routes the agent back to the other server tools for execution, so the alternative is named.

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

All prompt-guard-mcp toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources