Skip to main content
Glama
ellermanj

coinspot-mcp

by ellermanj

quote_swap_now

Read-only

Get a real-time swap quote by specifying the coin to sell, coin to buy, and amount. Use it to preview conversion rates before executing a trade.

Instructions

Get a Swap Now quote.

Args:
    cointypesell: Coin ticker to sell/swap from.
    cointypebuy: Coin ticker to receive.
    amount: Amount of the sell coin to swap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
cointypebuyYes
cointypesellYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no extra behavioral context such as rate limits, authentication needs, or error behavior, but it does not contradict the annotations either.

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?

The description is four lines, front-loads the purpose, and then lists arguments efficiently. Every part earns its place with no wasted text.

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 values need not be explained, and annotations cover safety. The parameters are well described. The only notable gap is the lack of sibling differentiation, but for calling the tool correctly the description is nearly complete.

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 must carry the full burden. It successfully defines all three parameters, clarifying the swap direction (sell/from, buy/to) and the meaning of amount. It lacks format details such as ticker format or amount precision.

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 states a specific verb and resource ('Get a Swap Now quote') and the word 'Swap' distinguishes it from buy/sell quote siblings. However, it does not explicitly name or contrast with the sibling tools, so full sibling differentiation is absent.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. Despite the presence of sibling quote tools, the description offers no routing information.

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