Skip to main content
Glama

ArcHive

arc_sessions

Lists the SessionPay sessions opened by an account: product, deposit, already settled, remainder, closed, expiry. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "owner": "<owner>"
    },
    "name": "arc_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes0x… address of the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does valuable work by disclosing the data source ('ArcHive API index') and an all-or-nothing failure contract ('if the list is briefly unavailable, the tool says so (never a partial list)'), but it says nothing about result volume, pagination/caps, ordering, or auth needs.

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 dense sentences with zero padding: the scope and returned fields come first, the failure-mode guarantee second. Every clause carries information an agent can act on.

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?

For a one-parameter read tool with no output schema, the description compensates by naming the fields returned and stating the no-partial-results behavior. Nothing essential for correct invocation is missing.

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 is fully documented in the schema (100% coverage, '0x… address of the account'), so the baseline is 3. The description adds only the notion that sessions are keyed to that owning account, not any new format or constraint detail.

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 SessionPay sessions opened by an account') and even enumerates the data fields returned. It is clearly distinct from a single-session lookup like arc_session_status, though it never names that sibling explicitly.

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: an agent infers this is the tool for enumerating all sessions belonging to one owner. There is no explicit when-to-use/when-not-to-use guidance and no pointer to arc_session_status for single-session queries, so the routing decision is left to inference.

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.