Skip to main content
Glama
Sign In
mcp-coinbase

mcp-coinbase

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sell_crypto

Place a cryptocurrency sell order on Coinbase. Use confirm=false for a preview, or confirm=true to execute the trade.

Instructions

Place a sell order for cryptocurrency on Coinbase. Set confirm to false (default) for a preview, or true to execute. Requires COINBASE_EMAIL and COINBASE_PASSWORD environment variables.

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": {
      "symbol": "<symbol>",
      "amount_crypto": "<amount_crypto>"
    },
    "name": "sell_crypto"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol to sell (e.g., "BTC", "ETH")
confirmNoIf false, returns preview only. If true, executes the order.
amount_cryptoYesAmount of cryptocurrency to sell (in crypto units)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Without annotations, the description discloses that execution is gated by confirm, that preview is default, and that environment variables are required. However, it does not detail order types or execution side effects.

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 concise sentences, front-loaded with purpose, then behavior and prerequisites. No wasted words.

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?

The tool has no output schema and no annotations, but the description covers purpose, preview/execution, and prerequisites. Missing return-value detail is a minor gap.

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 descriptions cover 100% of parameters, so the description adds no extra information beyond reiterating the confirm behavior already documented.

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 uses the specific verb 'Place' with the object 'a sell order for cryptocurrency on Coinbase,' clearly distinguishing it from sibling 'buy_crypto'.

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?

It provides explicit guidance on the confirm parameter (preview vs. execute), but does not explicitly name alternatives like buy_crypto or state when not to use it.

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