Skip to main content
Glama

create_merchant_session

Create a short-lived scoped merchant API credential. Parent merchant key required; sessions cannot delegate. Persist the returned token privately; it is returned once and cannot sign wallet payments.

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": {
      "name": "<name>",
      "scopes": "<scopes>",
      "expiresInSeconds": "<expiresInSeconds>"
    },
    "name": "create_merchant_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scopesYes
expiresInSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: short-lived lifetime, scoping, single-return of the token, private persistence, and two explicit capability exclusions (no delegation, no wallet-payment signing). It omits error behavior, rate limits, and how the credential is later revoked.

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?

Three tight sentences, front-loaded with the core action, then prerequisite, then handling instructions. No redundant restatement of the name or title.

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 no-annotation, no-output-schema mutation tool this covers the essentials an agent needs: required parent key, lifetime, scope limit, and one-time token handling. The main residual gap is the meaning of the individual scope values and the parameter naming.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters, so the description must compensate. It conveys that scoping and a lifetime exist ('scoped', 'short-lived') but never explains the 'name' field, the seconds unit or 60-86400 bounds on expiresInSeconds, or what the three scope enum values permit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Create a short-lived scoped merchant API credential.' That is clearly distinguishable from sibling challenge/rotation tools. It stops short of naming an alternative, but the credential-creation scope is unambiguous.

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

Usage Guidelines3/5

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

It states a prerequisite ('Parent merchant key required') and a restriction ('sessions cannot delegate'), which implies usage context. It never says when to choose this over the sibling credential-rotation or enrollment flows, so the agent must infer that from tool names.

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