Skip to main content
Glama

FiatDock

by com.fiatdock

Get order status

get_order_status
Read-onlyIdempotent

Check the status of an on/off-ramp order by partnerOrderId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partnerOrderIdYesOrder id returned when the session was created

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoReferral code if one was set
statusYesSESSION_CREATED -> PROCESSING -> COMPLETED | FAILED | CANCELLED | EXPIRED
createdAtNoISO 8601 session creation time
updatedAtNoISO 8601 time of the last status update (static under the current provider — no webhook exists, so the order stays SESSION_CREATED; ADR-0050)
customerIdNoCustomer id the session was created with
isBuyOrSellNoOrder direction

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / updatedAt / description
      Previous value: -"ISO 8601 time of the last webhook update"New value: +"ISO 8601 time of the last status update (static under the current provider — no webhook exists, so the order stays SESSION_CREATED; ADR-0050)"
  2. Changed2 schema fields changed
    • addedInput schema / properties / partnerOrderId / description
      Added value: +"Order id returned when the session was created"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "createdAt": {
+      "description": "ISO 8601 session creation time",
+      "type": "string"
+    },
+    "customerId": {
+      "description": "Customer id the session was created with",
+      "type": "string"
+    },
+    "isBuyOrSell": {
+      "description": "Order direction",
+      "enum": [
+        "BUY",
+        "SELL"
+      ],
+      "type": "string"
+    },
+    "ref": {
+      "description": "Referral code if one was set",
+      "type": "string"
+    },
+    "status": {
+      "description": "SESSION_CREATED -> PROCESSING -> COMPLETED | FAILED | CANCELLED | EXPIRED",
+      "type": "string"
+    },
+    "updatedAt": {
+      "description": "ISO 8601 time of the last webhook update",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, openWorldHint) already convey key behaviors. The description adds no extra details beyond the annotation coverage.

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, no extraneous words. Front-loaded with the core purpose.

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?

Given strong annotations and output schema, the description is adequate. Could add context about scope (e.g., only for partner orders) but not necessary.

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 coverage is 100% with clear parameter description. The description only mentions 'by partnerOrderId', adding marginal meaning to what the schema already provides.

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 clearly states the action (check status) and resource (on/off-ramp order by partnerOrderId). It is specific, but does not differentiate from sibling tools like create_offramp_session or get_quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus others. It simply describes the function without context of prerequisites or alternatives.

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

All FiatDock toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools are clearly separated by resource and action, but a few intentional bundles create mild selection overlap: token_report duplicates the data from token_price + token_safety, and address_intel overlaps eth_balance/usdc_balance plus safety. The descriptions explain the trade-offs well, so this is a minor rather than severe issue.

Naming Consistency4/5

Data-query tools follow a solid subject_metric pattern (token_price, usdc_balance, tx_status), while state-changing tools use verb_object (create_onramp_session, call_service). The pattern is readable and mostly consistent, but not a single uniform verb_noun convention throughout, so it falls just short of perfect.

Tool Count4/5

18 tools is above the typical 3-15 well-scoped range, but the server genuinely spans Base chain primitives, token intelligence, fiat ramps, and a marketplace. Each tool has a purpose, and the count is reasonable rather than bloated.

Completeness4/5

Core workflows are covered end-to-end: quote -> create on/off-ramp session -> order status; token price/safety/metadata/report; marketplace search/get/call; chain/tx primitives. Minor gaps exist, such as no order cancellation, no list-all-services endpoint, and no supported-country/method endpoint despite those details living in descriptions.

Resources