Skip to main content
Glama
Sign In
x207 mcp

x207 mcp

Official
by x207-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Order status

x207_order_status
Read-onlyIdempotent

Retrieve one order’s parties, budget, milestones, and status by hash, or list and filter circle marketplace orders by party and status.

Instructions

Orders of the circle's marketplace (read API GET /orders). With a hash: one order with its parties, budget, milestones and status. Without a hash: a page of orders, filtered by party and status. Use x207_search_listings to find offers before an order exists. An unknown hash is an error ("no order ... in circle"); an empty list is a normal result. Needs the read API (X207_BACKEND_URL).

Input Schema

NameRequiredDescriptionDefault
hashNoThe order hash. Leave out to list orders.
limitNoPage size, 1 to 200 (default 20); listing only.
partyNoOnly orders where this account is buyer or seller (listing only).
cursorNoThe nextCursor of the previous page; listing only.
statusNoOnly orders in this state, e.g. open, delivered or disputed (listing only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.0.5
    • addedInput schema / properties / cursor / description
      Added value: +"The nextCursor of the previous page; listing only."
    • changedInput schema / properties / limit / description
      Previous value: -"How many items, 1 to 200 (default 20)."New value: +"Page size, 1 to 200 (default 20); listing only."
    • changedInput schema / properties / status / description
      Previous value: -"Only orders with this status (listing only)."New value: +"Only orders in this state, e.g. open, delivered or disputed (listing only)."
  2. First observedv0.0.4

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond that: the backend environment variable requirement, the difference between an unknown-hash error and an empty-list result, and the return contents for single-order lookup.

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?

The description is dense but front-loaded and every clause contributes operational information: resource, hash/no-hash behavior, alternative sibling tool, error semantics, and environment dependency. There is no redundant restatement of the schema.

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?

For a read-only tool with five optional parameters and no output schema, the description covers the key behavioral branches, return contents for single-order lookup, filtering behavior for listing, error semantics, and backend dependency. Nothing essential for correct invocation 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 still adds useful meaning by explaining that hash switches between single-order retrieval and listing, and that listing can be filtered by party and status; cursor and limit details remain schema-driven.

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 names the specific resource (orders in the circle's marketplace), the underlying read API, and the two distinct modes: hash lookup for one order versus paginated listing. It also distinguishes this tool from x207_search_listings, making sibling selection clear.

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 explicitly says when to use a hash versus no hash, and directs the agent to x207_search_listings when looking for offers before an order exists. It also clarifies that an unknown hash is an error while an empty list is normal, which prevents misuse.

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