Regen Network MCP Server

get_sell_order

Retrieve detailed information about a specific marketplace sell order on the Regen Network by providing its unique sell order ID.

Instructions

Get specific marketplace sell order.

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": {
      "sell_order_id": "<sell_order_id>"
    },
    "name": "get_sell_order"
  }
}

Input Schema

Name	Required	Description	Default
`sell_order_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavior disclosure. It only states 'Get' which implies a read operation, but it does not mention side effects, rate limits, authorization requirements, or what happens if the order is not found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, consisting of a single phrase. While this is concise, it sacrifices completeness and clarity; a few more words to explain the parameter or context would improve it without losing conciseness.

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

Completeness3/5

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

Given the output schema exists, the description does not need to detail return values. However, it lacks any context about when to use this tool versus listing tools, error handling, or prerequisites. For a simple get-by-ID tool, it is adequate but minimal.

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

Parameters1/5

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

The description does not reference the sole parameter sell_order_id at all, despite schema description coverage being 0%. It fails to explain what the ID represents or how to obtain it, leaving the agent without necessary context beyond the schema.

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 it retrieves a specific marketplace sell order. The verb 'Get' and resource 'specific marketplace sell order' precisely communicate its function, and it distinguishes well from sibling list tools like list_sell_orders.

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 is provided on when to use this tool vs. alternatives such as list_sell_orders. The description does not mention prerequisites or indicate that it requires a sell_order_id to identify the specific order.

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

Deploy Server