Skip to main content
Glama

AgentPay

by io.github.yyxqqq777

Check AgentPay payment status

agentpay_payment_status
Read-onlyIdempotent

Return AgentPay payment configuration without charging: network, price, spending limit, payment mode, gateway URL, and agent wallet address. Call this before paid tools to verify the wallet is configured, or after a payment error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_walletNoIf true (default), include the derived agent wallet address from AGENT_PRIVATE_KEY.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / include_wallet
      Added value: +{
+  "default": true,
+  "description": "If true (default), include the derived agent wallet address from AGENT_PRIVATE_KEY.",
+  "title": "Include Wallet",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds the key behavioral trait that this operation does not charge, which is not covered by the annotations, providing extra transparency about side effects.

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?

The description is concise, consisting of two sentences that deliver essential information without unnecessary detail or repetition. It is well-structured and easy to parse.

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?

The description is complete for the tool's purpose: it states what is returned, when to call it, and that it does not charge. No additional context is needed for an agent to decide whether and how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'include_wallet' has a clear description explaining its effect ('include the derived agent wallet address') and its default value (true). This fully covers the parameter's semantics, leaving no ambiguity.

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?

The description clearly states the tool's function: returning AgentPay payment configuration. It enumerates the specific fields (network, price, spending limit, payment mode, gateway URL, agent wallet address) that will be returned, making the purpose unambiguous.

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?

The description provides explicit guidance on when to use the tool: 'Call this before paid tools to verify the wallet is configured, or after a payment error.' This directly tells the agent the appropriate contexts for invocation.

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

All AgentPay 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 has a clearly distinct target: one checks payment configuration, one queries China wholesale prices, and two cover Xiaohongshu note detail vs. user notes. There is no meaningful overlap or risk of an agent confusing one tool for another.

Naming Consistency3/5

The names share a prefix-style convention and use snake_case, but the pattern after the prefix is inconsistent: 'agentpay_payment_status' and 'china_wholesale_pricing_query' are noun-oriented, while both xhs tools are get-prefixed. This is readable and predictable enough, but not a uniform verb_noun convention.

Tool Count5/5

Four tools is within the well-scoped range and each tool earns its place: payment preflight, wholesale sourcing, XHS note detail, and XHS user posts. The set is compact without feeling artificially padded or thin.

Completeness4/5

The server covers its apparent paid-data-access workflows well: agents can verify payment setup, then call the relevant paid lookup tools. Minor gaps exist—there is no XHS search tool, no wholesale supplier-detail endpoint, and no transaction/payment history—but they are workable gaps rather than dead ends.

Resources