Armor Crypto MCP

Official

Overview Schema Source Related Servers Discussions Admin

unstake_quote

Retrieve a quote to unstake liquid staking derivatives. Specify wallet, input token, and amount to receive an unstake swap quote.

Instructions

Retrieve an unstake quote.

Expects a UnstakeQuoteRequestContainer, returns a SwapQuoteRequestContainer.

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": {
      "unstake_quote_requests": "<unstake_quote_requests>"
    },
    "name": "unstake_quote"
  }
}

Input Schema

Name	Required	Description	Default
`unstake_quote_requests`	Yes

Output Schema

Name	Required	Description	Default
`swap_quote_requests`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, and the description only mentions input/output types. It does not disclose whether the operation is read-only, requires authentication, or any side effects. For a quote retrieval, these details are important for safe invocation.

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?

Very brief at two sentences, which is concise but at the expense of useful detail. It could be improved by front-loading key behavioral information without expanding significantly.

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 of a nested request container and the presence of an output schema, the description lacks completeness. It does not explain what the quote contains, any constraints on inputs, or how the output should be interpreted.

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?

The description adds no information beyond the input schema. Schema descriptions already cover parameter fields (from_wallet, input_token, etc.), so the description merely restates the container type. With 0% schema description coverage, this is insufficient.

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 clearly states the action 'retrieve an unstake quote' and specifies the input/output container types. However, it lacks differentiation from sibling tools like 'stake_quote' and 'swap_quote', missing context on what makes an unstake quote unique.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The description does not help an agent decide between this and similar quote tools.

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