CoinStats MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

add-portfolio-transaction

Add cryptocurrency transactions to a manual portfolio in CoinStats, specifying coin, type, date, amount, and price for accurate tracking.

Instructions

Add a transaction to a manual portfolio.

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": {
      "coinId": "<coinId>",
      "type": "<type>",
      "date": "<date>",
      "amount": "<amount>",
      "price": "<price>"
    },
    "name": "add-portfolio-transaction"
  }
}

Input Schema

Name	Required	Description
`shareToken`	No	Portfolio share token
`coinId`	Yes	Coin ID
`type`	Yes	Transaction type
`date`	Yes	Transaction date in ISO format
`amount`	Yes	Transaction amount
`price`	Yes	Price per coin
`fee`	No	Transaction fee
`notes`	No	Transaction notes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Jan 3, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed2 schema fields changedSep 19, 2025
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedAug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Add a transaction' implies a write/mutation operation, but the description doesn't address critical aspects like required permissions, whether the operation is idempotent, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 that this is a mutation tool with no annotations, no output schema, and 8 parameters (5 required), the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, which are critical for an agent to use the tool correctly in a financial context.

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%, meaning all parameters are documented in the input schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain what 'manual portfolio' means or provide examples for 'type' values). With high schema coverage, the baseline score of 3 is appropriate.

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 ('Add a transaction') and the target resource ('to a manual portfolio'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'get-portfolio-transactions' or 'transactions-sync', which are related but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a portfolio share token), exclusions, or how it differs from sibling tools like 'transactions-sync' or 'get-portfolio-transactions', leaving the agent without context for tool selection.

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