Skip to main content
Glama

AIFEC

checkout_link

Read-only

The address of the checkout page with the customer's cart, where they review and pay. Payment always happens there.

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": "checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint=true annotation is consistent with the description, which correctly frames this as retrieving a URL rather than mutating state. Beyond the annotation, it discloses two useful behavioral facts: the returned page is tied to the customer's cart, and payment can only be completed on that page, which constrains how an agent should route the customer.

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?

Two short sentences, with the core payload (the checkout page address) front-loaded and the payment constraint following. Nothing is redundant or padding.

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 simple read-only tool with one optional parameter and no output schema, the description covers what is returned and the key constraint on where payment occurs. The session caveat lives in the schema, so the definition is essentially complete, with only explicit sibling routing left out.

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%, and the single session_id parameter is fully documented in the schema, including its purpose of preserving the same cart across calls. The description adds no further parameter detail, so the baseline of 3 applies.

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 precisely what the tool yields: the address of the checkout page holding the customer's cart. It is specific about the resource but phrased as a noun rather than a verb, and it never names a sibling like checkout_place or checkout_status to distinguish itself explicitly.

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?

Usage is only implied: the note that payment 'always happens there' hints that an agent should hand this URL to the customer to complete payment, but there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as checkout_place.

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