Skip to main content
Glama

ArcHive

arc_activity

Recent on-chain activity of the network's contracts (enclave registrations, sessions, settlements, bounties, verdicts), newest first. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).

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

Input Schema

NameRequiredDescriptionDefault
limitNonumber of events (1 to 50, default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work: it discloses the data source (ArcHive API index), the 'newest first' ordering, and an all-or-nothing guarantee ('if the list is briefly unavailable, the tool says so (never a partial list)'), which is exactly the kind of failure-mode detail an agent needs. However it never states that the operation is read-only, nor anything about auth, rate limits, or what a returned event looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both load-bearing: the first front-loads what the tool returns and its ordering, the second covers source and failure behavior. Nothing is repeated from the schema and no sentence is filler.

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 simple one-optional-param read tool with no output schema and no annotations, the description covers resource, event types, ordering, source, and failure semantics. The remaining gap is the shape of an individual event record, which is not described and, with no output schema, the agent must discover by calling.

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 'limit' parameter is fully documented in the schema, including range and default, so the schema does the heavy lifting. The description adds only the ordering guarantee ('newest first'), which indirectly tells the agent that limit truncates from the newest end; no further parameter meaning is supplied.

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?

States a specific resource ('recent on-chain activity of the network's contracts') and enumerates the event categories it returns (enclave registrations, sessions, settlements, bounties, verdicts), which lets an agent distinguish this aggregate feed from single-domain siblings like arc_sessions or arc_bounties. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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: the enumeration of mixed event types suggests this is the tool for a cross-entity recent-activity glance, while the per-domain siblings would be used for focused queries. There is no explicit when-to-use or when-not-to-use statement, and no mention of ordering alternatives or prerequisites.

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.