Skip to main content
Glama

neet_report_lite

Read-onlyIdempotent

FREE lite NEET report: price, 24h change, market cap, canonical status, cluster signal and consensus score, safety band, net inflow needed for 2x / 5x / 10x, and the wallets-in-profit headline. Section detail, cluster events, full ladder and clone sightings are capped. Use it to triage whether the full neet_report is worth $0.02.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so safety is covered; the description adds genuinely new behavior: the call is free, several sections (detail, cluster events, full ladder, clone sightings) are deliberately capped, and the alternative costs $0.02. It does not describe rate limits or response shape, but with annotations carrying the safety profile this is solid added context.

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 sentences, front-loaded with the field inventory, then the capping caveat, then the routing advice. The field list is dense but each item earns its place by telling the agent what it will actually receive. Minor cost: the run-on enumeration is harder to scan than a short list.

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?

With no parameters and no output schema, the description carries the full burden of explaining return values, and it does so field by field, including what is truncated. An agent knows what it gets, what it won't get, and when to escalate to the paid sibling.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter claims are made or needed.

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 enumerates the exact payload (price, 24h change, market cap, canonical status, cluster signal, consensus score, safety band, net inflow for 2x/5x/10x, wallets-in-profit) and frames itself as the lite/free counterpart to neet_report. An agent can tell precisely what this returns and how it differs from the fuller sibling without opening any schema.

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?

It gives an explicit use case: triage whether the paid neet_report ($0.02) is worth buying, which implicitly routes to the alternative when full detail is needed. It stops short of stating an explicit when-not condition (e.g. 'do not use when you need the full ladder'), so it is clear but not exhaustive.

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.