Skip to main content
Glama

ArcHive

arc_bounties

Lists the sealed bounties of BOTH levels (open: SealedBounty; verified: SealedBountyVerified, where only enclaves on a chip declared by a Proof of Cloud auditor count) and the products each level settles: level, contract, protocol, product, balance, deadline, pause, open or not. 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_bounties"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyOpenNotrue = only the open bounties

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: data comes from the ArcHive API index, the verified level is gated on a Proof of Cloud auditor chip declaration, and an unavailable index is reported as an error rather than a partial list. Gaps remain on pagination/volume limits and any auth prerequisites.

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?

Front-loaded with the resource and scope, and every clause carries information (levels, returned fields, data source, failure mode). The first sentence is a long run-on that packs the level semantics into a nested parenthetical, which slightly hurts scannability.

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 no-annotation, no-output-schema list tool, the description compensates well by enumerating the returned fields and the record shape. It omits ordering, pagination, and result-count expectations, which an agent would need for large result sets.

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?

The single parameter onlyOpen is fully documented in the schema (100% coverage), so the schema already does the work. The description never references the parameter or explains what 'open' means in relation to the 'open or not' return field, so it adds nothing beyond the baseline.

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 verb ('Lists') and a specific resource ('sealed bounties'), and even enumerates the two levels (SealedBounty, SealedBountyVerified) and the fields each record carries. It does not name a sibling to contrast with, but 'Lists' vs. arc_bounty_prepare_create is recoverable from the verb alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement, and no routing to alternatives such as arc_bounty_prepare_create or arc_activity. The only guidance is the implicit fact that this is a read-only enumeration, which an agent would have to infer from the verb.

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.