hashlock-mcp

Official

by Hashlock-Tech

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Browse the RFQ board

list_open_rfqs

Read-onlyIdempotent

Browse the public RFQ board to find open or negotiating quote requests you can respond to, with optional filters for direction, base asset, and quote asset.

Instructions

Browse the public RFQ board: requests you can quote with respond_to_rfq (your own appear too). Returns the 100 newest requests that are open or negotiating, each with rfqId, direction, amounts, assets, ask price and expiry. Filters are optional and combine with AND. Private orders never appear here; read one with get_rfq and the id from its link.

Input Schema

Name	Required	Description
`direction`	No	sell_base: the requester gives the base asset; buy_base: the requester receives it
`base_asset`	No	Filter by base asset ("SYMBOL@chain" or id)
`quote_asset`	No	Filter by quote asset

Output Schema

Name	Required	Description	Default
`error`	No	Set instead when the call failed
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.11.1Nov 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / direction / description

Added value: +"sell_base: the requester gives the base asset; buy_base: the requester receives it"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "error": {
+      "additionalProperties": {},
+      "description": "Set instead when the call failed",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "is_retryable": {
+          "type": "boolean"
+        },
+        "message": {
+          "type": "string"
+        },
+        "recovery_hint": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "askPrice": {
+            "description": "Total ask; null if none",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "baseAmount": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rfqId": {
+            "description": "Request id",
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedv0.10.0Oct 29, 2026

addedInput schema / properties / base_asset

Added value: +{
+  "description": "Filter by base asset (\"SYMBOL@chain\" or id)",
+  "type": "string"
+}

addedInput schema / properties / direction

Added value: +{
+  "enum": [
+    "sell_base",
+    "buy_base"
+  ],
+  "type": "string"
+}

removedInput schema / properties / page

Removed value: -{
-  "description": "1-based page number. Default 1.",
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / pageSize

Removed value: -{
-  "description": "Page size, 1-100. Default 20.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / quote_asset

Added value: +{
+  "description": "Filter by quote asset",
+  "type": "string"
+}

First observedv0.4.0May 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes further with real behavioral detail: a hard result cap of 100, newest-first ordering, the included statuses (open or negotiating), and the exclusion of private orders. It does not say what happens past the 100th result (truncation vs. no pagination), which is the one operational gap.

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?

Four tight sentences, each carrying distinct information: purpose, result shape and cap, filter behavior, and the private-order exclusion with its redirect. Scope and the exclusion are front-loaded, with zero filler or restated title text.

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?

With an output schema present, the description need not document return fields, and annotations already carry the read-only safety profile. Given only 3 optional parameters, the description covers the remaining unknowns an agent would care about: result limit, ordering, which statuses are included, and what is deliberately absent.

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 100%, including a documented direction enum, so the baseline is 3. The description adds meaning the schema does not: that every filter is optional and that multiple filters are combined with AND, which changes how an agent composes calls.

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?

States a specific verb and resource ('Browse the public RFQ board') and immediately frames it in terms of the action it enables ('requests you can quote with respond_to_rfq'), tying it to a sibling. It further distinguishes itself by noting 'your own appear too' and that 'Private orders never appear here', which separates it from my_rfqs and get_rfq without opening either schema.

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?

Explicitly routes the agent: private orders must be read via get_rfq with the id from its link, and quoting is done with respond_to_rfq. It also states filters are optional and combine with AND. It stops short of naming an alternative for 'show only my own RFQs' versus my_rfqs, so the coverage of alternatives is strong but not exhaustive.

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

Deploy Server