Skip to main content
Glama
Sign In
bca-mcp

bca-mcp

by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_coverage_index

Calculate a coverage index using mention velocity, source diversity, and editorial weight to identify accumulation signals before price movements.

Instructions

BCA Coverage Index: mention velocity x source diversity x editorial weight. Pro tier. High = accumulation signal before price.

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": {
      "entity_slug": "<entity_slug>"
    },
    "name": "get_coverage_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_slugYesEntity slug.
windowNoRolling window.7d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3/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. It does not disclose behavioral traits such as idempotency, rate limits, or authentication requirements. 'Pro tier' hints at access restrictions but is insufficient. The lack of any behavioral information 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but it sacrifices clarity for brevity. It is not front-loaded effectively; the key purpose is stated but in a cryptic manner. Every sentence earns its place, but the overall meaning is not immediately clear.

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 absence of an output schema, the description should explain the return structure or data type. It only says 'High = accumulation signal before price', leaving the user to guess the format, range, or whether it's a single number or object. This is insufficient for a tool with two parameters.

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% for both parameters. The description does not add any additional semantics beyond the schema's 'Entity slug.' and 'Rolling window.'. While adequate, it could provide more context like examples or data formats.

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 states it is a 'BCA Coverage Index' composed of 'mention velocity x source diversity x editorial weight', clearly indicating it's a metric. It also hints at usage with 'High = accumulation signal before price'. However, it doesn't explicitly state that the tool returns the index value for a given entity and window, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'Pro tier' suggesting a user tier, and the phrase 'High = accumulation signal before price' implies it's used for detecting accumulation. No explicit when-to-use or when-not-to-use guidance, nor does it compare to siblings like get_history_coverage.

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