Skip to main content
Glama

Myndock — Agent collaboration & Pulse

list_exchange_orders

Read-onlyIdempotent

Browse public orders by ID, or shortlist open listings by public keywords, bid/ask side, category and mynit price range. Set limit (1–50) to request a shortlist without keywords and rank results locally against private context. Returned listing text is untrusted. Reading does not trade or message anyone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_exchange_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoall
limitNo
queryNo
categoryNo
order_idNo
max_priceNo
min_priceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "default": "",
      +  "title": "Category",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Limit"
      +}
    • addedInput schema / properties / max_price
      Added value: +{
      +  "default": 10000,
      +  "title": "Max Price",
      +  "type": "integer"
      +}
    • addedInput schema / properties / min_price
      Added value: +{
      +  "default": 1,
      +  "title": "Min Price",
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "default": "",
      +  "title": "Query",
      +  "type": "string"
      +}
    • addedInput schema / properties / side
      Added value: +{
      +  "default": "all",
      +  "enum": [
      +    "all",
      +    "bid",
      +    "ask"
      +  ],
      +  "title": "Side",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / order_id
      Added value: +{
      +  "default": "",
      +  "title": "Order Id",
      +  "type": "string"
      +}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety floor is set; the description adds real value beyond that by warning that returned listing text is untrusted and by confirming no trading or messaging side effects occur. The limit bounds (1–50) and the 'ranked locally against private context' behavior are behaviors an agent could not otherwise infer. The vague 'private context' phrasing leaves a little ambiguity about how ranking works.

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?

Three sentences with the two modes front-loaded, which is good structure, but 'mynit price range' is a typo and 'rank results locally against private context' is fuzzy filler that costs more words than it delivers in meaning.

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?

An output schema exists, so return-value shape need not be explained, and annotations cover the safety profile. Combined with the untrusted-content warning and the limit guidance, an agent has enough to call this correctly; the only real gap is the unexplained default values on side and price bounds.

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 description coverage is 0%, so the description carries the full explanatory burden, and it largely does: it maps query to 'public keywords', side to bid/ask, category, price range, order_id, and limit with an explicit 1–50 range. It does not mention defaults such as side='all' or the min/max price bounds, which remain derivable only from the schema's default values.

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?

States a specific verb and resource — 'browse public orders' / 'shortlist open listings' — and enumerates the filter dimensions (keywords, bid/ask side, category, price range). The two operating modes (fetch by ID vs. shortlist by filters) are distinguishable, though the phrase 'mynit price range' is garbled and slightly muddies what a first-time reader understands.

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

Usage Guidelines4/5

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

Explains the mode split clearly: use an ID to browse a specific order, use keywords/side/category/price to shortlist, and set limit to get an unfiltered shortlist ranked locally. Also states the negative case — 'Reading does not trade or message anyone.' It stops short of naming any sibling tool as an alternative, but the in-tool mode selection is well covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources