Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_social_pulse

Track social velocity including mentions, engagement, and sentiment across Twitter, Reddit, and Discord for any entity.

Instructions

Social velocity: mentions, engagement, sentiment across Twitter/Reddit/Discord. Pro tier. Returns BCA_NOT_IMPLEMENTED if social ingest not yet wired.

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

Input Schema

NameRequiredDescriptionDefault
windowNo
entity_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns BCA_NOT_IMPLEMENTED if social ingest is not wired, which is useful, but does not mention other behaviors like rate limits, idempotency, or authentication requirements.

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?

Two sentences, front-loaded with the core purpose. The structure is efficient, though it could be improved by adding brief parameter descriptions.

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 parameter count and lack of output schema, the description covers the main function and an important error case, but missing parameter explanations and return format details leave gaps for the agent.

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

Parameters1/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 explain parameters. It does not describe 'entity_slug' or 'window' at all, leaving the agent without guidance on what values to provide or their meaning.

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 returns social velocity metrics (mentions, engagement, sentiment) across Twitter/Reddit/Discord, and distinguishes it from siblings like get_sentiment and get_social_signals by specifying the platforms and 'Pro tier' limitation.

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 implies usage for social metrics but does not explicitly state when to use this tool over alternatives like get_social_signals or get_sentiment. The 'Pro tier' note provides some context but lacks exclusion criteria or when-not-to-use guidance.

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