Skip to main content
Glama
Sign In
@giftcardshop/mcp

@giftcardshop/mcp

by i2dor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get order status

get_order_status

Check an order's payment status and reveal code availability. Get the current state of an order using its ID.

Instructions

Check an order: payment state and whether the reveal link (the code) is available yet.

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": {
      "orderId": "<orderId>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. The verb 'Check' conveys a read-only operation, and the description specifies the observable outputs. It does not mention error behavior or side effects, but for a simple status query this is adequate.

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?

Single sentence, front-loaded with the action, with no wasted words. The parenthetical clarifies the reveal link without adding bulk.

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 single-parameter read tool with no output schema, the description covers the essential return values (payment state, reveal link availability) and implies the input. It lacks explicit parameter guidance and edge-case behavior, but these are minor for this tool.

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%, and the description does not mention the orderId parameter or its format/meaning beyond the schema's property name. Since the description must compensate for low schema coverage and does not, this is a clear gap.

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') and resource ('order'), and clarifies exactly what is returned (payment state, reveal link availability). This clearly distinguishes it from sibling tools like create_order and get_product, which operate on different resources or actions.

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?

The description gives clear context: use this when you need an order's payment status or reveal link availability. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous relative to the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools