Skip to main content
Glama
Sign In
CoinStats MCP Server

CoinStats MCP Server

Official
by CoinStatsHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-portfolio-coins

Retrieve cryptocurrency portfolio holdings with profit/loss data and risk metrics from CoinStats. Use a share token to access specific portfolio information.

Instructions

Get a list of portfolio coins with P/L and other data displayed on CoinStats web.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-portfolio-coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
shareTokenNoPortfolio share token. You can get your share token from the portfolio you want to retrive data from by clicking Share button on CoinStats web app portfolio tracker section - top right.
pageNoPage number
limitNoNumber of results per page
includeRiskScoreNoInclude risk score: true or false. Default - false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get') but doesn't specify authentication requirements, rate limits, pagination behavior (beyond parameters), error conditions, or what 'other data' includes. For a tool with 4 parameters and no output schema, this is insufficient behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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. It's appropriately sized for a read operation and front-loaded with key information. There's no unnecessary verbosity, though it could be slightly more informative without losing conciseness.

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 tool's complexity (4 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return format, data structure, error handling, or how the 'shareToken' is obtained (though the schema covers this). For a tool that retrieves financial portfolio data, more context is needed for effective agent use.

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?

The description adds no parameter-specific information beyond what's already in the input schema, which has 100% coverage. It doesn't explain relationships between parameters (e.g., how 'page' and 'limit' interact) or provide usage examples. Since the schema does the heavy lifting, 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 tool's purpose: 'Get a list of portfolio coins with P/L and other data displayed on CoinStats web.' It specifies the verb ('Get'), resource ('portfolio coins'), and key data elements (P/L and other data). However, it doesn't explicitly differentiate from sibling tools like 'get-portfolio-transactions' or 'get-portfolio-chart,' which reduces it from a perfect score.

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 share token), exclusions, or comparisons to sibling tools like 'get-coins' or 'get-portfolio-transactions.' This leaves the agent with minimal 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.

Deploy Server

Other Tools