Skip to main content
Glama

ForthClear Liquidation Marketplace

Get order status

get_order_status
Read-only

Check status, tracking, and the inspection deadline for an order you placed. Requires sign-in with buyer access. OAuth discovery: /.well-known/oauth-authorization-server (scope buyer:read).

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

Input Schema

NameRequiredDescriptionDefault
order_idYesForthClear order id

Output Schema

NameRequiredDescriptionDefault
statusYes
currencyYes
order_idYes
quantityYes
trackingYes
created_atYes
updated_atYes
next_actionsYes
ship_by_dateNo
total_amountNo
payment_releasedNo
issue_reported_atNo
inspection_deadlineNo
delivery_received_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "created_at": {
      +      "type": "string"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "delivery_received_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "inspection_deadline": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "issue_reported_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_actions": {
      +      "items": {
      +        "properties": {
      +          "deadline": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "type",
      +          "description"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "order_id": {
      +      "type": "integer"
      +    },
      +    "payment_released": {
      +      "type": "boolean"
      +    },
      +    "quantity": {
      +      "type": "integer"
      +    },
      +    "ship_by_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "total_amount": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "tracking": {
      +      "properties": {
      +        "carrier": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "expected_delivery": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "number": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "number"
      +      ],
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "updated_at": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "order_id",
      +    "status",
      +    "quantity",
      +    "currency",
      +    "tracking",
      +    "created_at",
      +    "updated_at",
      +    "next_actions"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing the authentication requirement ('Requires sign-in with buyer access') and the exact OAuth scope (buyer:read) plus discovery endpoint, which is real pre-call context an agent cannot get from annotations. It does not, however, discuss failure modes such as an order id the caller does not own.

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 tight sentences with the payload description front-loaded and auth requirements following. The OAuth discovery URL is slightly technical clutter but earns its place as actionable setup information. No redundant restatement of the 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?

With an output schema present, the description need not explain return values, and the single parameter is fully documented in the schema. Adding the auth scope and access requirement fills the main remaining gap for a read tool. Only the lack of guidance on obtaining a valid order id keeps it from a 5.

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 order_id parameter is documented as 'ForthClear order id'. The description adds only the implicit constraint that the order must belong to the caller ('an order you placed'), with no format, type, or sourcing guidance beyond that. Baseline 3 applies when the schema carries the parameter documentation.

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 opens with a specific verb and resource ('Check status, tracking, and the inspection deadline for an order') and even enumerates the three data points returned, which distinguishes it from siblings like get_dispute_status and get_quote_status. The phrase 'an order you placed' adds buyer-side scoping. It does not explicitly name a sibling, so it stops short of a 5.

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 implied rather than stated: 'for an order you placed' signals this is the buyer-side lookup and not the seller-side path, which is mild routing guidance. There is no explicit when-not-to-use or named alternative (e.g., list_my_orders for finding an order id, cancel_order for acting on one).

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