Skip to main content
Glama
Sign In
shingou

shingou

by shingou-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Latest sentiment

get_sentiment
Read-onlyIdempotent

Retrieve the latest news sentiment signal for up to 50 crypto symbols per request. Sentiment is recalculated hourly for each asset.

Instructions

Latest news-sentiment signal per symbol (batch up to 50 in one call — one signal per asset per hour, so never poll faster than hourly). On the free plan, symbols outside BTC-USD/ETH-USD/SOL-USD are 24h delayed: check timestamp and disclose staleness.

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": {
      "symbols": "<symbols>"
    },
    "name": "get_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesShingou symbols, e.g. ["BTC-USD","ETH-USD"] (see get_symbols)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedInput schema / properties / symbols / description
      Previous value: -"Shingou symbols, e.g. [\"BTC-USD\",\"ETH-USD\"] (see list_symbols)"New value: +"Shingou symbols, e.g. [\"BTC-USD\",\"ETH-USD\"] (see get_symbols)"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds significant behavioral info beyond annotations: batching limit, rate limit (hourly), free plan delay, timestamp disclosure requirement. No contradictions with readOnlyHint/idempotentHint.

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 concise sentences, each dense with actionable information. Front-loaded with main purpose and batching. No fluff.

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

Completeness4/5

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

Covers key aspects: batching, rate limits, plan differences, timestamp. Lacks explanation of return value structure, but acceptable for simple signal tool without output schema.

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 covers 100% of parameters. Description adds symbol format ('Shingou symbols'), example, and reference to get_symbols. Baseline 3 plus extra value.

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?

Description clearly states it returns 'Latest news-sentiment signal per symbol' with batching up to 50. Distinguishes from sibling 'get_sentiment_history' via 'latest' and from 'get_symbols' by purpose.

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?

Explicitly states when to use: batching allowed, polling frequency (hourly). Notes free plan delays and need to check timestamp. Does not explicitly contrast with get_events, but provides clear context.

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