Skip to main content
Glama
kukapay

crypto-orderbook-mcp

by kukapay
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

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

  • Latest release: v1.0.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: calculate_orderbook focuses on a single exchange, while compare_orderbook aggregates data across multiple exchanges. There is no overlap in functionality, and the descriptions clearly differentiate between individual analysis and comparative analysis.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (calculate_orderbook, compare_orderbook) with clear, descriptive names that reflect their actions. The naming is uniform and predictable across the tool set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a crypto orderbook domain. While the tools cover calculation and comparison, there are likely missing operations such as fetching raw orderbook data, historical analysis, or alerts for imbalances, making the scope incomplete.

    Completeness2/5

    The tool set is severely incomplete for a crypto orderbook server. It lacks basic CRUD operations like fetching raw orderbook data, updating or deleting calculations, and monitoring features. The two tools provide only calculation and comparison, leaving significant gaps for agent workflows.

  • Average 3.9/5 across 2 of 2 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

  • This repository is licensed under MIT License.

  • 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?

    With no annotations provided, the description carries full burden for behavioral disclosure. It mentions what the tool returns but lacks details on rate limits, authentication needs, error handling, or whether it's a read-only operation. The description is minimal beyond basic functionality.

    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 well-structured and concise, with a clear purpose statement followed by parameter and return value sections. Every sentence adds value without redundancy, making it easy to parse.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness3/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    Given the complexity of a financial calculation tool with no annotations and no output schema, the description is moderately complete. It covers parameters and return values but lacks behavioral context like performance implications or error conditions, which are important for such operations.

    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?

    The description adds significant meaning beyond the input schema, which has 0% description coverage. It explains each parameter's purpose with examples (e.g., 'binance', 'BTC/USDT', '1.0%'), clarifying semantics that the schema alone does not provide.

    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 purpose with specific verbs ('calculate') and resources ('order book depth and imbalance'), specifying it's for a trading pair on an exchange. It distinguishes from the sibling tool 'compare_orderbook' by focusing on calculation rather than comparison.

    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 the sibling 'compare_orderbook' or other alternatives. It mentions the parameters but offers no context about appropriate use cases or exclusions.

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

  • Behavior3/5

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

    With no annotations provided, the description carries the full burden. It discloses the tool's behavior (comparison across exchanges, Markdown table output) and default values, but lacks details on potential limitations like rate limits, authentication requirements, or what happens with unsupported exchanges. It doesn't contradict any annotations.

    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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value: the first establishes the tool's function, the parameter explanations provide necessary context, and the return statement clarifies output format. 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?

    Given 3 parameters with 0% schema coverage and no output schema, the description does well by explaining all parameters and the return format. However, as a comparison tool with no annotations, it could benefit from mentioning performance considerations or data freshness, though the current information is largely complete for basic usage.

    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 compensate. It adds meaningful context for all 3 parameters: explains 'symbol' as trading pair with an example, clarifies 'depth_percentage' as percentage range from mid-price with default, and describes 'exchanges' as list of IDs with default. However, it doesn't specify format for exchange IDs or valid ranges for depth_percentage.

    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 specific action ('compare order book depth and imbalance'), the resource ('for a trading pair across multiple exchanges'), and the output format ('returning a Markdown table'). It distinguishes itself from the sibling tool 'calculate_orderbook' by focusing on comparison across exchanges rather than calculation.

    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 provides clear context for when to use this tool (comparing order books across exchanges) and mentions a default behavior ('default: all supported exchanges'). However, it doesn't explicitly state when NOT to use it or provide alternatives to the sibling tool 'calculate_orderbook'.

    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

crypto-orderbook-mcp MCP server

Copy to your README.md:

Score Badge

crypto-orderbook-mcp 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/kukapay/crypto-orderbook-mcp'

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