Skip to main content
Glama

Vigil Website MCP

get_checkout

Read-onlyIdempotent

Read a checkout started with create_checkout.

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": {
      "checkout_id": "<checkout_id>"
    },
    "name": "get_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description's only added behavior is the creation precondition; it says nothing about error behavior for an unknown/expired checkout_id or the shape of the returned object, which is the remaining gap.

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?

A single short sentence with the resource and its provenance front-loaded; there is no filler. Its brevity borders on under-specification rather than verbosity, but nothing in it is wasted.

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

Completeness2/5

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

For a one-parameter read with no output schema, the description is thin: it never explains what a checkout represents, what data comes back (line items, totals, status), or whether checkouts expire. Annotations carry the safety story, but the missing return context is a real gap for an agent deciding whether this call answers its question.

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%, so the schema documents only that checkout_id is a required string. The description's mention of create_checkout implies where the ID originates, but it gives no format, prefix, or validity guidance for the single parameter, so it does not compensate for the coverage gap.

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?

Uses a specific verb (Read) with a specific resource (checkout), and pairs it with the sibling that produces the resource (create_checkout), so an agent can distinguish read from create without opening the schema. It stops short of 5 because it never says what a checkout object actually contains, leaving the resource somewhat abstract.

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 through the dependency on create_checkout, which usefully signals the precondition that a checkout must already exist. There is no explicit when-to-use statement, no guidance on what to do when the ID is unknown or expired, and no named alternative among the other siblings.

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