Skip to main content
Glama

Bitcoin new-project radar ($0.01)

btc_radar_latest
Read-only

Fetches newly launched Bitcoin L1 tokens and inscriptions with stage, verdict, risk flags, and sources; x402 payment occurs only when data is available.

Instructions

PAID $0.01 USDC on Base via x402, from the caller's own wallet. Latest list of newly launched Bitcoin L1 tokens/inscriptions (BRC-20, Runes, Alkanes, Stamps) with stage, verdict, risk flags and sources. If no data is published the API returns 503 before payment. Not investment advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that each call costs $0.01 USDC on Base via x402, charged from the caller's own wallet — a material side effect that annotations do not capture. It also states that a missing feed returns 503 before payment, so the agent knows a failure is not billed, and adds a not-investment-advice caveat on the verdict data.

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?

Three tight sentences with no repetition, and the failure-mode note is placed right after the content summary. The cost/payment clause leads the description rather than the purpose, which slightly delays the 'what does this do' signal, and the disclaimer sentence is boilerplate but arguably earns its place on a tool emitting verdicts.

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 output schema, the description carries the return-value burden and does so by enumerating the payload fields (stage, verdict, risk flags, sources). Cost, payment rail, and the pre-payment 503 behavior cover the operational facts an agent needs before calling a paid endpoint.

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 schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering or pagination inputs are accepted.

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?

States a specific verb and resource: the latest list of newly launched Bitcoin L1 tokens/inscriptions, naming the four sub-types (BRC-20, Runes, Alkanes, Stamps) and the fields returned (stage, verdict, risk flags, sources). That clearly separates it from the sibling lookups token_risk, token_risk_batch and project_info, which are per-asset queries rather than a discovery feed.

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 only implied: a zero-parameter 'latest list' tool is recognizably a discovery entry point, and the 503-on-no-data note tells the agent what happens on an empty feed. However, it never says when to reach for this instead of project_info or token_risk, nor whether it should be called before those lookups, so routing between siblings 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.