Skip to main content
Glama
Sign In
shingou

shingou

by shingou-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Typed market events

get_events
Read-onlyIdempotent

Retrieve recent classified market events for a crypto symbol, with headlines and source links. Critical hack, regulation, or delisting events are flagged.

Instructions

Recent classified market events for a symbol. Kill-switch trio: hack_exploit, regulation, delisting — the reference integrations stand aside for 24h after one. Report the event headline and source link, not just a risk flag.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events (default 20)
symbolYesOne Shingou symbol, e.g. BTC-USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations confirming read-only behavior, the description reveals the 'kill-switch trio' behavior where reference integrations stand aside for 24 hours, adding important behavioral context.

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 very concise, using two sentences plus a directive to convey purpose, behavioral quirks, and output expectations without unnecessary words.

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?

Given rich annotations, full schema documentation, and the lack of output schema, the description adequately explains what the tool does, how to use it, and what to report from the response.

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 coverage is 100%, but the description adds value by noting the default limit (20) and providing an example symbol format, which are not fully captured in schema 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 retrieves 'Recent classified market events for a symbol' and distinguishes itself from siblings like sentiment tools by specifying event types and reporting expectations.

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 provides usage guidance by instructing to report the event headline and source link, but it does not explicitly state when not to use this tool or suggest alternatives.

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