Skip to main content
Glama

Arc fresh lite

arc_fresh_lite

Lightweight newly created Arc token launch feed with sell check ($0.001). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does well: it discloses the price ($0.001 per call), the payment rails (x402 with USDC on Arc, Base or Solana, or XNT on X1), and the two-step pay-and-retry protocol. It stops short of describing what the returned feed contains, how many entries to expect, or whether repeated calls are cached or billed again.

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, front-loaded with what the tool is, followed by cost and the payment procedure. The $0.001 figure is stated twice, which is minor redundancy, but nothing is wasted overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid data-feed tool with no output schema and no annotations, the description covers the commercial and invocation mechanics thoroughly. It omits what the feed actually returns (fields, recency window, chain coverage), which an agent would need to judge result usefulness.

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 `payment` parameter is already documented in the schema as a signed x402 payload that completes the purchase. The description reinforces the two-phase flow but adds little semantic detail about the parameter itself, so the baseline of 3 applies.

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 and scope: a feed of newly created Arc token launches, with a sell check, in a lightweight variant. An agent can tell it is a data feed rather than an action tool. It does not, however, differentiate itself from the sibling arc_fresh_launches, leaving the 'lite' distinction implicit.

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?

It gives explicit invocation guidance for the payment handshake: call once without `payment` to get terms, sign with your own wallet, then call again with `payment`. That is real how-to-use context, but there is no guidance on when to pick this tool over arc_fresh_launches or other launch feeds, and no stated prerequisites beyond payment.

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