Skip to main content
Glama

Get a Stripe Checkout URL that tops up this key’s balance

credits_checkout

Creates a one-time Stripe Checkout Session for a credit pack, bound to the calling live key’s account. When the payment completes the credits land on that balance; poll GET /keys/me. This is what a 402 topUp.checkoutEndpoint points at. No charge, consumes no quota. (POST https://app.deepvalues.ai/api/v1/credits/checkout — no charge; needs a connected account or a dv_sk_ key)

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": {
      "pack": "<pack>"
    },
    "name": "credits_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYesCredit pack to buy, e.g. "1000". The `credits_packs` tool lists the packs on sale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, and the description adds materially beyond them: no charge is incurred, no quota is consumed, the session is bound to the *live* key's account, and there is an auth prerequisite ('needs a connected account or a dv_sk_ key'). It also explains the side effect's completion path (credits land on the balance; poll GET /keys/me), which is the key behavioral fact for a non-idempotent write.

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 action and scope, then the trigger condition, then the cost/auth notes. The trailing parenthetical repeats the endpoint URL and the 'no charge' fact already stated in the prior sentence, which is mild redundancy but the payload stays tight overall.

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 single-parameter, side-effecting tool with no output schema, it covers trigger, auth prerequisites, cost, side effect, and the follow-up verification call. The only small gap is that it never explicitly says the call returns a checkout URL — that is only recoverable from the title — so an agent must infer the return value.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains that `pack` is a credit pack with example value "1000" and points at credits_packs. The description adds no additional semantics about format, validation, or pack naming beyond what the schema carries, so the baseline of 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 concrete verb and resource: 'Creates a one-time Stripe Checkout Session for a credit pack, bound to the calling live key's account.' It names the exact scope (the calling key's balance) and distinguishes itself from siblings like credits_packs ('lists the packs on sale') and keys_me ('poll GET /keys/me' to confirm the result).

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?

Gives an explicit trigger condition: 'This is what a 402 topUp.checkoutEndpoint points at,' so an agent knows to call it when a request fails for insufficient credits. It also routes the agent to credits_packs to enumerate purchasable packs and to keys_me to verify completion, leaving almost nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources