Skip to main content
Glama
Sign In

Insight Pre-Trade Safety

by io.github.imokokok
OverviewDiscussionsAdmin

get_market_quote

Read one reviewed venue market: pool/market metadata, pinned quote context and venue constraints for Base, Monad, Solana or Hyperliquid. Use it before preparing or gating a trade when the agent needs the reviewed profile or market id. Do not use it as execution authorization or for prices outside the reviewed venues. Returns the market record, reviewed profile ids and current quote context. Deprecated alias: prefer trade_guard with op "market_quote". Removed on 2027-01-06.

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": {
      "venue": "<venue>"
    },
    "name": "get_market_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueYesReviewed venue to quote
marketNoHyperliquid perp market
venuesNoBase venue ids to inspect
profile_idNoReviewed pool/profile id. PancakeSwap V3: base-pancakeswap-v3-usdc-usdt-100, bnb-pancakeswap-v3-usdt-usdc-100, bnb-pancakeswap-v3-usdt-wbnb-100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / profile_id / description
      Previous value: -"Reviewed pool/profile id"New value: +"Reviewed pool/profile id. PancakeSwap V3: base-pancakeswap-v3-usdc-usdt-100, bnb-pancakeswap-v3-usdt-usdc-100, bnb-pancakeswap-v3-usdt-wbnb-100"
    • changedInput schema / properties / venue / enum
      Previous value: -[
-  "base_uniswap_v3",
-  "base_aerodrome",
-  "base_pancakeswap_v3",
-  "base_quickswap_v2",
-  "base_venue_identity",
-  "monad_uniswap_v3",
-  "monad_hanji",
-  "solana_jupiter",
-  "hyperliquid_perp"
-]New value: +[
+  "base_uniswap_v3",
+  "base_aerodrome",
+  "base_pancakeswap_v3",
+  "bnb_pancakeswap_v3",
+  "base_quickswap_v2",
+  "base_venue_identity",
+  "monad_uniswap_v3",
+  "monad_hanji",
+  "solana_jupiter",
+  "hyperliquid_perp"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it marks the operation as a read, scopes it to a reviewed allowlist of venues, states it is not an authorization signal, and discloses the deprecation plus removal date. It stops short of noting permission prerequisites or rate limits, which keeps it off a 5.

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

Conciseness4/5

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

Four sentences, front-loaded with purpose, then usage, then exclusions, then return shape, then the deprecation notice. Every sentence contributes, though the deprecation sentence could arguably lead or be trimmed given its verbosity.

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?

There is no output schema, but the description compensates by naming what is returned (market record, reviewed profile ids, current quote context). Combined with explicit scope limits and the migration path to trade_guard, an agent has enough to call it correctly; only auth and error behavior are unstated.

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

Parameters3/5

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

Schema description coverage is 100% with two enumerated parameters, so the schema already explains venue, market, venues and profile_id. The description only echoes the concepts ('venue constraints', 'market id') without adding format, interaction or conditional rules (e.g. when market vs venues applies). Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Read one reviewed venue market') and enumerates what is returned: pool/market metadata, pinned quote context and venue constraints across four named chains. It also identifies itself as a deprecated alias for trade_guard op "market_quote", so an agent can distinguish it from the sibling that supersedes it.

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 states exactly when to call it ('before preparing or gating a trade when the agent needs the reviewed profile or market id'), when not to ('not as execution authorization', 'not for prices outside the reviewed venues'), and names the preferred alternative (trade_guard with op "market_quote"), including a removal date.

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

All Insight Pre-Trade Safety toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources