Skip to main content
Glama
Sign In

Terminal 7

by io.github.LinkMarine777
OverviewDiscussionsAdmin

get_signals

Signal families (radar, holders, chart, scores, kols, flow, rising, combo) firing on stonkfun coins, and the T7 bot's paper buys / sells, oldest first, with unix times.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNoonly this coin (its mint address)
limitNoat most this many (default 200, max 500)
sinceNounix seconds: only newer events

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 the full behavioral burden. It usefully discloses return content, oldest-first ordering, and unix time formatting, but omits read-only/auth/rate-limit/pagination behavior beyond what the schema already states.

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?

A single front-loaded sentence with no filler; the parenthetical list efficiently enumerates signal families. Every phrase contributes to describing the tool's output.

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?

For a 3-param read tool with no output schema or annotations, the description adequately conveys returned content, ordering, and time format. It stops short of describing the response envelope or per-event fields, but the schema fully documents parameters.

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% and all three parameters have descriptions. The description adds little parameter-specific meaning beyond 'stonkfun coins' and 'oldest first' for mint/since, so the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states specific content: enumerated signal families and the T7 bot's paper buys/sells, with ordering and time format. It clearly distinguishes from generic siblings like get_coin or get_top by focusing on signals, though it does not name alternatives explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative tool guidance. The only context is 'on stonkfun coins,' which implies scope but does not help an agent choose between get_signals and get_coin/get_top/get_usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Terminal 7 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources