Skip to main content
Glama

CON, Central Operating Network

Solana Launch Index

launch_index
Read-only

The CON Launch Index: per day, Solana coins rated by CON and the share that stood 70% or more lower one hour later, overall, per risk class and per finding. Without a date: the latest day and the last 14 days.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDay as YYYY-MM-DD (Berlin day), optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description adds useful substance — the exact 70%/one-hour threshold definition and the default 14-day window when no date is supplied — but says nothing about data freshness, latency, or result size for what is evidently an aggregated daily dataset.

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?

Two tight sentences with the resource front-loaded and the default-behavior caveat held to the end. Density is high and nothing is wasted, though the telegraphic 'per risk class and per finding' phrasing is terser than it needs to be for readability.

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 single optional-parameter, read-only tool with no output schema, the description conveys the return shape adequately (per-day, with overall and broken-out breakdowns) and covers the no-date case. Gaps remain in unexplained domain terms ('CON', 'finding') that a pointer to define_term would have resolved.

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 date parameter is already documented as optional YYYY-MM-DD (Berlin day). The description's added value is the default semantics when the parameter is omitted, which is genuinely beyond the schema, but the 'Berlin day' timezone framing merely echoes the schema rather than extending it.

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 names a specific resource (the CON Launch Index) and enumerates exactly what it returns: daily Solana coins rated by CON, plus the share that fell 70%+ within an hour, broken out overall / per risk class / per finding. An agent can tell this is an index/metrics retrieval tool, though the verb is implicit and nothing distinguishes it from the sibling rating_log.

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?

The only usage signal is the conditional behavior 'Without a date: the latest day and the last 14 days', which effectively says this is the default call form. There is no explicit when-to-use versus rating_log or check_coin, and no stated prerequisites or exclusions, so routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources