Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

track_narrative

Track real-time narrative strength across crypto sectors including AI agents, RWA, DePIN, modular, memes, Bitcoin L2s, SocialFi, and GameFi using the BCA Narrative Strength Score.

Instructions

Real-time narrative strength (AI agents, RWA, DePIN, modular, memes, Bitcoin L2s, SocialFi, GameFi). Composite of BCA Narrative Strength Score. Starter tier.

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": {
      "narrative": "<narrative>"
    },
    "name": "track_narrative"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNo
narrativeYese.g. 'ai-agents', 'rwa', 'depin', 'modular'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations present. Description does not disclose behavioral traits such as whether it is read-only, if it requires authentication, or what 'Starter tier' implies (limitations). Does not describe caching or rate limits.

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?

Single sentence, concise and front-loaded with key information. Could be more structured with separate lines for value and limitations, but efficient overall.

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?

No output schema, and description fails to specify what the tool returns (e.g., numeric score, units, range). Missing details on 'Composite of BCA Narrative Strength Score' meaning. Incomplete for an agent to fully understand the output.

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?

Parameter narrative has a description with examples in schema, but window parameter is undocumented. Description adds example narratives for context, but does not otherwise enhance meaning beyond schema. Schema coverage is 50%, but description partially compensates.

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?

Description clearly states it provides real-time narrative strength for specific categories like AI agents, RWA, etc. Verb 'track' is clear. However, it does not differentiate from sibling 'get_narrative_strength', which likely has similar function.

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?

No guidance on when to use this tool vs alternatives. No mention of prerequisites or when not to use. Implied usage for getting narrative strength but lacks explicit direction.

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