Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get an order, or search them

eurodns_order_get
Read-onlyIdempotent

Retrieve order details with lines and delivery status, filtering by ID, statuses, dates, search term, or pagination.

Instructions

Returns one order with its lines and their delivery status by id, or searches orders when id is omitted — by statuses, startDate and endDate, a free-text term, or deliveryInProgress — paged with page and size. Use it to learn what happened to a subscription that was ordered but never became active; the filters are ignored when id is given. The invoice raised for an order is in eurodns_invoice_get, not here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the order to return with its lines. Omit it to search orders with the filters below.
pageNo1-based page number. There is no page meaning everything: walk pages until a short one comes back.
sizeNoResults per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.
termNoThe search term allowing to search orders based on the description of its order lines.
endDateNoThe parameter allowing to search orders before the given date
statusesNoKeep only orders in these payment statuses, e.g. PAID, PENDING_PAYMENT or REFUSED.
ordersIdsNoThe list of order identifiers.
sortFieldNoResult field to sort on, spelled as in the response items. Unsorted when omitted.
sortOrderNoASC or DESC; only read with sortField.
startDateNoThe parameter allowing to search orders after the given date
orderLineIdsNoThe list of order line id related to the orders.
deliveryInProgressNoThe delivery status of the orders. An order delivery is considered in progress once the order payment has been processed but no all order lines are delivered yet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.10.0
    • addedInput schema / properties / deliveryInProgress
      Added value: +{
+  "description": "The delivery status of the orders. An order delivery is considered in progress once the order payment has been processed but no all order lines are delivered yet.",
+  "type": "boolean"
+}
    • addedInput schema / properties / endDate
      Added value: +{
+  "description": "The parameter allowing to search orders before the given date",
+  "type": "string"
+}
    • addedInput schema / properties / id / description
      Added value: +"Numeric id of the order to return with its lines. Omit it to search orders with the filters below."
    • addedInput schema / properties / orderLineIds
      Added value: +{
+  "description": "The list of order line id related to the orders.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / ordersIds
      Added value: +{
+  "description": "The list of order identifiers.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based page number. There is no page meaning everything: walk pages until a short one comes back.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / sortField
      Added value: +{
+  "description": "Result field to sort on, spelled as in the response items. Unsorted when omitted.",
+  "type": "string"
+}
    • addedInput schema / properties / sortOrder
      Added value: +{
+  "description": "ASC or DESC; only read with sortField.",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / startDate
      Added value: +{
+  "description": "The parameter allowing to search orders after the given date",
+  "type": "string"
+}
    • addedInput schema / properties / statuses
      Added value: +{
+  "description": "Keep only orders in these payment statuses, e.g. PAID, PENDING_PAYMENT or REFUSED.",
+  "items": {
+    "description": "The order payment status. - CART: no payment attempts were made. - CREDIT_LINE: an invoice will be sent in relation to the order. - EXPIRED_CART: no payment attempts were made and the cart end of life has been reached. - FRAUD: a payment attempt was flagged as potentially fraudulent. - NO_CHARGE: no payment required. - PAID: a payment has been accepted and completed. - PENDING_PAYMENT: a payment attempt has been initiated. - QUOTE: a payment is required to process the quote - QUOTE_AUTHORIZATION: an authorization approver needs to validate the quote. - REFUSED: a payment attempt has been declined.",
+    "enum": [
+      "CART",
+      "PAID",
+      "CREDIT_LINE",
+      "PENDING_PAYMENT",
+      "REFUSED",
+      "NO_CHARGE",
+      "FRAUD",
+      "QUOTE",
+      "EXPIRED_CART",
+      "QUOTE_AUTHORIZATION"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / term
      Added value: +{
+  "description": "The search term allowing to search orders based on the description of its order lines.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id"
-]
  2. First observedv0.9.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context: id changes the operation from search to single-order fetch, filters are ignored when id is present, and results are paged. This goes beyond the structured annotations without contradicting them.

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?

Three dense sentences front-load the primary behavior, then add a practical use case and a sibling-tool pointer. Every sentence contributes information, with no repetition of schema details.

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

Completeness5/5

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

Given the rich input schema, output schema, and comprehensive annotations, the description covers the essential decision points: single-get versus search, filter behavior, pagination, and where to find invoices. Nothing critical for invoking the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantic value by explaining that filters are ignored when id is given, grouping the search parameters, and clarifying pagination behavior. It also distinguishes order lines from invoices, helping the agent understand the domain model.

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?

The description clearly states that the tool returns one order with its lines and delivery status by id, or searches orders when id is omitted. It also differentiates itself from eurodns_invoice_get, making its scope unambiguous among the sibling tools.

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

Usage Guidelines5/5

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

It gives an explicit use case ('learn what happened to a subscription that was ordered but never became active') and states when filters apply versus when they are ignored. It also directs invoice-related needs to eurodns_invoice_get, providing a clear alternative.

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