Skip to main content
Glama
Sign In
openpulsechain

openpulsechain

Official
by openpulsechain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Opportunity Signal

get-opportunity-signal
Read-onlyIdempotent

Assess PulseChain token opportunities with a composite score from 0-100. Combines momentum, volume, buy pressure, safety, whale activity, and liquidity fragility to generate actionable trading signals.

Instructions

[PRO] Composite opportunity score (0-100) for a PulseChain token. Combines momentum, volume spike, buy pressure, safety, whale activity, and MC/liquidity fragility. Returns confidence level and graceful degradation for partial data. Requires OPENPULSECHAIN_API_KEY.

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": {
      "address": "<address>"
    },
    "name": "get-opportunity-signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract address (0x...)

Output Schema

NameRequiredDescriptionDefault
opportunity_scoreYesComposite score 0-100
gradeYesGrade: A, B+, B, C, D, F
direction_hintYesstrong_opportunity, bullish_momentum, neutral_positive, neutral, bearish_pressure, avoid
confidenceYeshigh, medium, low, insufficient_data
factorsYesIndividual factor scores
kill_signalsYesOverride signals that force score to 0
data_completenessYesfull, partial_no_history, safety_only, minimal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate non-destructive, read-only, idempotent behavior. The description adds that it returns a confidence level and handles partial data gracefully, which is valuable context beyond the annotations.

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?

Two sentences efficiently convey purpose, components, and key features. No wasted words, and the most critical info is front-loaded in the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return format details are covered. The description explains the composite nature, graceful degradation, and authentication requirement. For a single-parameter tool, this is sufficient.

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 coverage is 100% with one parameter 'address' fully described in the schema. The description does not add new parameter meaning, so baseline score applies.

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 composite opportunity score (0-100) for PulseChain tokens, combining six specific components like momentum and volume spike. This distinguishes it from siblings like get-token-safety or get-token-sentiment, which focus on individual aspects.

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

Usage Guidelines4/5

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

The description mentions the requirement for an API key and labels it as '[PRO]', indicating a paid tier. While it doesn't explicitly compare to siblings, the composite nature implies use for overall opportunity assessment. Some guidance on when not to use would improve clarity.

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