Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_entity_mentions

List editorial mentions for a crypto entity with sentiment scores and article links. Use to track narrative evolution over time.

Instructions

Timeline of editorial mentions for an entity: sentiment score, sentiment bucket, and article linkback per mention. Use this to reconstruct narrative arc over time.

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": {
      "slug": "<slug>"
    },
    "name": "list_entity_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesEntity slug (chain, project, person, ticker).
limitNoMax mentions (default 50).
sinceNoISO 8601 lower bound for published_at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.4/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 full burden. It discloses output shape (sentiment score, bucket, article linkback) but omits ordering, pagination, default limit (50), and behavior for parameters like since.

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, compact and front-loaded with key output elements. No wasted words, but could be slightly more structured with explicit output description.

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?

No output schema is provided, so the description should compensate. It mentions sentiment score, bucket, and article linkback but does not specify mention text, ordering, or how limit/since affect results. Partially complete.

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%, so the schema already documents all three parameters. The description adds minimal value beyond 'timeline' context, adhering to baseline expectation.

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 a timeline of editorial mentions with sentiment score, bucket, and article linkback per mention. This distinguishes it from siblings like search_news (general search) and get_sentiment (aggregate sentiment).

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 provides a use case: 'Use this to reconstruct narrative arc over time.' However, it does not explicitly state when not to use this tool or suggest alternatives among the many sibling tools.

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