Skip to main content
Glama

list_merchant_sessions

List retained merchant session metadata without credentials. Parent merchant key required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_merchant_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/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 disclose two useful behavioral traits: no credentials are needed and only metadata (not secrets) is returned, and that only "retained" sessions are included. It does not cover pagination, ordering, rate limits, or whether the listing is scoped to the caller's own merchant, which leaves meaningful gaps for a list operation.

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?

Two short sentences, front-loaded with the operation and its scope; nothing is padded. The only inefficiency is that the second sentence introduces a requirement the schema cannot honor, adding words that create confusion rather than clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no output schema, the description does convey the resource, the credential-free mode, and the retained-session filter. However, it omits how results are shaped or bounded and asserts a required merchant key that the schema does not expose, so the agent still cannot tell whether the key comes from session context or an argument.

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?

The input schema declares zero properties and sets additionalProperties=false, meaning no arguments are accepted. The description's claim that a "Parent merchant key required" therefore conflicts with the schema and could lead an agent to pass a parameter that will be rejected. This actively misleads rather than adding meaning, so it falls below the 0-param baseline of 4.

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 states a specific verb and resource ("List ... merchant session metadata") plus a scope qualifier ("retained", "without credentials"), which distinguishes it from sibling mutators like create_merchant_session and revoke_merchant_session that share the same session noun. It stops short of naming any list-style sibling for contrast, so it is clear but not fully differentiated.

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?

"List retained merchant session metadata" implies an inspection/audit use case, and "without credentials" signals the tool works in a credential-free context. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for session data, leaving the agent to infer the intent.

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