Skip to main content
Glama

ArcHive

arc_products

Lists the products of Arc's enclave network (price with its unit, shares, settlement, minimum bond, state). 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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyActiveNotrue = only the active products

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It does add genuine behavioral value by disclosing the data source (ArcHive API index) and the failure contract: if the list is briefly unavailable the tool reports that rather than returning a partial list, which matters for callers who would otherwise trust a truncated result. It does not mention authentication, rate limits, freshness/caching, or response shape beyond the field list.

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 compact sentences that lead with the resource and its returned fields, then the reliability caveat. The parenthetical field list is dense but each token carries information; nothing 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?

With no output schema, the description usefully compensates by enumerating the returned fields, and it flags the no-partial-list behavior. For a single-parameter read tool this is close to sufficient; only auth expectations and the meaning of onlyActive remain unaddressed.

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?

Only one parameter (onlyActive) exists and the schema already documents it at 100% coverage, so the baseline is 3. The description never mentions the flag or clarifies what 'active' means (e.g. not settled/expired), adding no meaning beyond the schema.

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 and resource — 'Lists the products of Arc's enclave network' — and enumerates the fields returned (price with unit, shares, settlement, minimum bond, state). This is far more than a restatement of the name, but it never differentiates the tool from siblings such as arc_pricing or arc_product_scaffold, so an agent must infer the boundary itself.

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?

The description says what the tool returns but gives no when-to-use guidance, no prerequisites, and no mention of when a sibling (e.g. arc_pricing, arc_enclaves) would be the better choice. Only the implicit read-only listing purpose hints at usage.

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.