Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Make a top-up pay link for my owner

top_up

Create a payment link to fund your balance. Give pay_link to your human owner: it works for 7 days; they tick a box to agree to the waiver, then pay on Stripe's page (USD). Humans always use pay_link. Only for a machine payment by your own agent wallet set for_agent_wallet: true to also get url, the direct Stripe page (about 30 minutes). Then poll top_up_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amount_centsYes500, 1000, 2000, 5000 or 10000 US cents.
passport_tokenNoYour amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in.
for_agent_walletNotrue only when your own agent wallet pays (machine payment): the answer then also holds url. Never give url to a human.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount_cents / anyOf
      Previous value: -[
-  {
-    "const": 500,
-    "type": "number"
-  },
-  {
-    "const": 1000,
-    "type": "number"
-  },
-  {
-    "const": 2000,
-    "type": "number"
-  }
-]New value: +[
+  {
+    "const": 500,
+    "type": "number"
+  },
+  {
+    "const": 1000,
+    "type": "number"
+  },
+  {
+    "const": 2000,
+    "type": "number"
+  },
+  {
+    "const": 5000,
+    "type": "number"
+  },
+  {
+    "const": 10000,
+    "type": "number"
+  }
+]
    • changedInput schema / properties / amount_cents / description
      Previous value: -"500, 1000 or 2000 US cents."New value: +"500, 1000, 2000, 5000 or 10000 US cents."
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / amount_cents / description
      Added value: +"500, 1000 or 2000 US cents."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint false, openWorldHint true, non-idempotent), and the description adds real behavioral context they do not: the link's 7-day validity, the waiver checkbox step, USD/Stripe flow, the ~30 minute window for the direct url, and an explicit 'Never give url to a human' warning. It does not fully spell out what the response contains, but it substantially exceeds the annotation baseline.

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-loads the purpose in the first sentence and keeps the whole thing short, with each clause carrying usable information (validity, waiver, currency, machine path). The middle sentences are dense and slightly run-on but nothing is wasted.

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?

For a 3-parameter write tool with no output schema, the description conveys the key return artifact (pay_link or url), the prerequisite flow, and the follow-up call. The main gap is that it never touches authentication (passport_token) beyond what the schema says, but the schema fully covers that.

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 already documented in the schema, including allowed amount values, the passport_token fallback, and the for_agent_wallet/url contract. The description restates the for_agent_wallet behavior and amount context but adds little beyond the schema, so the baseline 3 applies.

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: 'Create a payment link to fund your balance.' It also names the follow-up sibling 'top_up_status', so an agent can distinguish the two top-up-related tools without opening either schema.

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?

Explicitly routes the two usage paths: 'Humans always use pay_link' versus machine payment via for_agent_wallet: true, and it tells the agent to 'poll top_up_status' afterward. When-to-use, who-uses-what, and the alternative are all covered.

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

All AgentMart toolsInspect
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.

Resources