Skip to main content
Glama
Adity-star

crypto_price_tracker

by Adity-star
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The single tool follows a clear verb_noun pattern ('get_crypto_market_info'), which is consistent with standard naming conventions and leaves no room for inconsistency.

    Tool Count1/5

    The server has only one tool, which is extremely thin for a typical MCP server. A crypto price tracker would typically need additional capabilities such as historical data, symbol discovery, or alerts to be useful.

    Completeness3/5

    The tool covers the core need of fetching current exchange rates, but it lacks obvious complementary features like historical data or a way to list supported cryptocurrencies, leaving notable gaps for a price tracking domain.

  • Average 4.1/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • 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. It states that it returns current exchange rates, but it does not mention that it makes an external API call (to Alpha Vantage), potential rate limits, authentication requirements, or possible failure modes. For a tool that performs network I/O, this lack of transparency is a notable 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 concise and well-structured. It front-loads the purpose, then lists parameters with examples, and concludes with the return type. Every sentence is informative, and there is no redundant or vague content.

    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?

    Given the tool's simplicity (two parameters, no output schema, no annotations), the description covers the essential information: purpose, parameters, and return value. However, it could be more complete by describing the exact structure of the returned exchange rates or noting any constraints (e.g., maximum number of symbols). Still, it is sufficient for a basic getter tool.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters5/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    The input schema has no descriptions for its parameters (0% coverage), so the description fully compensates. It provides clear semantics for crypto_ids ('Comma-separated list of cryptocurrency symbols (e.g., 'BTC,ETH')') and currency ('The fiat currency to compare against (default: 'USD')'), including an example and the default value. This adds significant value beyond what the schema provides.

    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 clearly states the tool's function: 'Get market information for one or more cryptocurrencies using Alpha Vantage.' It specifies the verb (get), the resource (market information for cryptocurrencies), and the data source (Alpha Vantage). This is unambiguous and distinct even in the absence of sibling tools.

    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?

    The description gives clear context that this tool is used for obtaining cryptocurrency market information, and it explains the required parameters. It does not explicitly mention alternatives or when not to use it, but since there are no sibling tools, this is adequate. It could be improved by noting that it provides current exchange rates but not historical data, but this is not a major gap.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

mcp-crypto-server MCP server

Copy to your README.md:

Score Badge

mcp-crypto-server MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Adity-star/mcp-crypto-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server