Skip to main content
Glama
alsk1992

Strata MCP

by alsk1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Sonar quote

strata_quote
Read-only

Get a short-lived Sonar quote by providing a market and a human amount such as 0.1 SOL or $20. Returns expected output, fees, price impact, and expiry.

Instructions

Request a short-lived Sonar quote. Use a market label and a human amount such as 0.1 SOL, 20 USDC, or $20; exact input atoms remain available for advanced clients. Returns expected output, fees, price impact, and expiry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYesBuy or sell the market's base asset.
amountNoHuman input amount, for example 0.1 SOL, 20 USDC, or $20.
marketYesMarket label such as SOL/USDC, or its public market ID.
amountInAtomsNoAdvanced: exact input amount in the input token's smallest atomic unit.
maximumToleranceBpsNoThe most you accept below the quoted output, in basis points (default 0: the quoted output exactly). This is YOUR choice. It is not price impact — price_impact_pct in the response is measured from the book and is not a setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.17
    • addedInput schema / properties / amount
      Added value: +{
+  "description": "Human input amount, for example 0.1 SOL, 20 USDC, or $20.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / amountInAtoms / description
      Previous value: -"Exact input amount in the input token's smallest atomic unit."New value: +"Advanced: exact input amount in the input token's smallest atomic unit."
    • changedInput schema / required
      Previous value: -[
-  "market",
-  "side",
-  "amountInAtoms"
-]New value: +[
+  "market",
+  "side"
+]
  2. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / maximumToleranceBps
      Added value: +{
+  "default": 0,
+  "description": "The most you accept below the quoted output, in basis points (default 0: the quoted output exactly). This is YOUR choice. It is not price impact — price_impact_pct in the response is measured from the book and is not a setting.",
+  "maximum": 1000,
+  "minimum": 0,
+  "type": "integer"
+}
    • removedInput schema / properties / slippageBps
      Removed value: -{
-  "default": 0,
-  "description": "Optional maximum execution tolerance in basis points. The default 0 requires exact quoted output.",
-  "maximum": 1000,
-  "minimum": 0,
-  "type": "integer"
-}
  3. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive behavior, so the bar is lower. The description adds meaningful context by noting the quote is short-lived, returns an expiry, and includes fees and price impact. No contradiction with annotations.

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?

Two tight sentences: the first states purpose and lifespan, the second covers how to specify inputs and what the response contains. No filler or redundant restatement of schema details.

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, so the description correctly enumerates the key return fields: expected output, fees, price impact, and expiry. Combined with the well-described input schema and annotations, this is sufficient for an agent to invoke the tool correctly, though it never explicitly says the quote does not execute a trade.

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%, so the baseline is 3. The description's examples for amount and market mirror the schema rather than adding new meaning, and it adds little beyond pointing at advanced atom inputs. maximumToleranceBps and side are left to the schema.

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 uses a specific verb and resource ('Request a short-lived Sonar quote') and states the tool's output. It is clearly a quoting tool, but it does not explicitly distinguish itself from the execution sibling strata_trade or other market tools.

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

Usage Guidelines3/5

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

The description gives usage instructions for inputs ('Use a market label and a human amount') and notes advanced atom inputs, but it never says when to prefer this tool over alternatives such as strata_trade. Usage context is implied rather than explicit.

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

Deploy Server

Other Tools