Regen Network MCP Server

list_sell_orders_by_seller

Retrieve sell orders placed by a specific seller on the Regen Network blockchain marketplace. Enter the seller's address to filter and paginate through their active sell orders for ecological credits.

Instructions

List sell orders by seller.

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": {
      "seller": "<seller>"
    },
    "name": "list_sell_orders_by_seller"
  }
}

Input Schema

Name	Required	Description	Default
`seller`	Yes
`page`	No
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 27, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only states a simple listing operation without discussing read-only behavior, authentication needs, rate limits, or pagination details beyond what the schema provides.

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 a single sentence, which is concise and front-loaded. However, it may be too terse for a tool with three parameters and no schema descriptions.

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

Completeness2/5

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

Given the complexity (3 params, 1 required) and presence of an output schema, the description should provide context on what the tool returns (list of sell orders) and any default behavior. It only states 'list sell orders by seller,' leaving gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate. It adds minimal value: 'by seller' indicates seller as a filter, but does not explain the meaning of seller, page, or limit beyond their names. No format or allowed values noted.

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 'List sell orders by seller' clearly states a verb and resource. It distinguishes from siblings like list_sell_orders and list_sell_orders_by_batch by specifying the filtering criteria, but the differentiation is minimal as the tool name itself conveys the same.

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 versus alternatives (e.g., list_sell_orders, list_sell_orders_by_batch). The description lacks context for usage scenarios or exclusions.

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

Deploy Server