Skip to main content
Glama

Check linked payment method

get_payment_method
Read-onlyIdempotent

Check whether the verified phone has a card linked for agentic checkout, and if so its brand/last4 and current spending cap in dollars. If nothing is linked, points to /link-card. Requires session_token from verify_code.

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": {
      "session_token": "<session_token>"
    },
    "name": "get_payment_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's added value is the auth dependency on verify_code and a preview of the returned payload. It does not describe failure modes for an invalid or expired session_token, which keeps it below a 5.

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?

Three short sentences with no filler; the purpose and return contents are front-loaded. The prerequisite is tacked on at the end rather than leading, 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?

There is no output schema, yet the description names the key returned fields (brand/last4, spending cap) and the no-card branch, which is enough for a single-parameter read tool. Only error/expiry behavior for the token is left unstated.

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?

Only one parameter exists and the schema gives it no description (0% coverage), so the description must compensate. It does so by stating where session_token comes from ('from verify_code'), which is real meaning beyond the schema's bare string type.

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 ('Check whether') plus the exact resource ('card linked for agentic checkout') and even enumerates the returned fields (brand/last4, spending cap in dollars). This clearly separates it from the mutating sibling link_payment_method.

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

Usage Guidelines4/5

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

Establishes a clear context (agentic checkout) and a prerequisite ('Requires session_token from verify_code'), and notes that when nothing is linked the flow points to /link-card. It stops short of explicitly naming link_payment_method as the alternative to call, leaving that inference to the agent.

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