Skip to main content
Glama
Sign In

TRNCH

by fun.trnch
OverviewDiscussionsAdmin

Top Robinhood Chain tokens of the last 24 hours

trnch_top_24h
Read-onlyIdempotent

What performed on Robinhood Chain in the last 24 hours: the best tokens that entered the Trnch Heat (new tokens screened by Trnch), with their peak and current multiple since entry, and a link to trade them at the best route. Rugged, dumped and flagged tokens are left out. Past performance, not a prediction. No key needed.

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": "trnch_top_24h"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tokens (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, and the description adds real context on top: rugged/dumped/flagged tokens are excluded from results, the ranking metric is multiple since Heat entry (peak and current), each entry carries a trade link, and no API key is required. The only gap is that the ranking metric itself is only loosely defined ('peak and current multiple since entry').

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?

Front-loads the time window and subject, then layers in data contents, exclusions, and the disclaimer in a compact block. The risk disclaimer and 'no key needed' earn their place, though the promotional register ('the best tokens') is slightly softer than a neutral specification.

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?

For a one-optional-parameter, read-only, no-output-schema tool, the description covers what is ranked, over what window, what is filtered out, what fields come back, and that no auth is needed. Nothing an agent needs to decide to call it is missing.

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 the single optional limit parameter is fully documented in the schema, including its default of 10 and the 1-20 range. The description adds nothing about the parameter, so the baseline 3 is correct.

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?

States a specific resource and scope: top-performing tokens on Robinhood Chain over the last 24 hours, drawn from the Trnch Heat screening set. That is clearly distinguishable from siblings like trnch_heat (all newly screened tokens) and trnch_stats, though it does not name those siblings explicitly to force the contrast.

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?

Usage is implied by the time window and ranking semantics ('what performed in the last 24 hours'), so an agent can infer this is the go-to for recent top performers. There is no explicit when-not guidance and no pointer to trnch_heat or trnch_stats as the alternative for different views.

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

All TRNCH 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