Registrai Arc data

Arc apps: daily USDC

arc_apps_daily

Read-onlyIdempotent

USDC received per day by Arc apps and directory projects since mainnet's first day (2026-09-16), counted from every USDC transfer into their contracts, before any index rule (USD, transfers, distinct payers). One app (up to 31 days) or all apps (up to 7 days). Use this when asked how much USDC an app or exchange on Arc receives, or how a project's flows changed since launch.

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_apps_daily"
  }
}

Input Schema

Name	Required	Description
`to`	No	YYYY-MM-DD (UTC), inclusive.
`app`	No	Index app id (domain:…, integration:…) or entity:<directory slug>. Omit for all apps.
`from`	No	YYYY-MM-DD (UTC), inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

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 and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the counting methodology (every USDC transfer into contracts, before index rules), the historical start date, and asymmetric day-range limits depending on whether an app is specified. It does not describe the shape of the returned series.

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 what is measured before the usage clause, and no filler. The parenthetical '(USD, transfers, distinct payers)' is slightly opaque and sits awkwardly mid-sentence, but it is short and does not obscure the main point.

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 must convey what comes back, and 'USDC received per day' plus the measurement basis does that adequately for an analytics query. Combined with full schema coverage and annotations covering the safety profile, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not carry: omitting the app parameter caps the range at 7 days while a single app allows up to 31 days. That constraint materially changes how an agent should set 'app', 'from' and 'to'.

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 states a precise verb+resource: USDC received per day by Arc apps and directory projects, counted from every USDC transfer into their contracts. The 'per day' framing plus the start date (2026-09-16) separates it cleanly from a weekly sibling, and the scope ('before any index rule') tells the agent what is being measured.

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: 'how much USDC an app or exchange on Arc receives, or how a project's flows changed since launch.' It also states the operational envelope (one app up to 31 days, all apps up to 7 days). It stops short of naming an alternative such as a weekly or history tool, so there is no explicit when-not guidance.

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

All Registrai Arc data tools Inspect

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

Need Help?