Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_narrative_strength

Assess narrative consolidation versus fading by computing eigenvector centrality on co-mention graphs in rolling windows.

Instructions

Co-mention graph centrality: which narratives are consolidating vs fading. Pro tier. Uses eigenvector centrality in rolling windows.

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_narrative_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoRolling window.
entity_slugYesEntity slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.7/5.0
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. It discloses the method (eigenvector centrality in rolling windows) but does not cover behavioral traits like computational cost, authentication requirements, rate limits, or what happens with missing data.

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 two sentences, front-loaded with key information, and contains no fluff. Every sentence adds value.

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?

With no output schema and only 2 parameters, the description covers the purpose and method but lacks details on return format, score interpretation, or any edge cases. It is minimally adequate but leaves gaps.

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 100%, but the description adds context that the rolling window is used to track consolidation vs fading, enhancing understanding beyond the schema's brief descriptions.

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 measures narrative strength via co-mention graph centrality, specifically identifying consolidating vs fading narratives. It distinguishes from sibling tools like get_sentiment or get_social_pulse by focusing on narrative centrality.

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' implying premium access but gives no explicit guidance on when to use this tool vs alternatives, nor when not to use it. Usage context is somewhat implied by the name but not explicitly stated.

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