Skip to main content
Glama

Recent Gateway crossings

gateway_activity
Read-only

Retrieve recent token crossings between Zenith EVM and Canton, decoded from Gateway contract events with per-token counts by direction.

Instructions

Recent token crossings between Zenith EVM and Canton, decoded from the Gateway contract's own events (Collected, NativeCollected, Minted, Released), with per-token counts by direction.

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": "gateway_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
includeSetupNoAlso list registration events (wrappers, vaults, metadata)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing that results are decoded from the contract's own events, enumerating those event types (Collected, NativeCollected, Minted, Released), and explaining that output is aggregated by direction — which tells the agent this is a derived, possibly partial view rather than authoritative state.

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?

A single dense sentence that front-loads the core purpose (recent crossings between the two chains) and appends scope detail efficiently. The parenthetical event list is long but earns its place by naming the source semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return shape and partially does ('per-token counts by direction'). It still omits result ordering, windowing/freshness of 'recent', what limit constrains, and what includeSetup adds to the response, leaving an agent guessing about pagination and result granularity.

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 50%: includeSetup is documented in the schema, but limit only carries min/max/default with no meaning. The description never mentions limit, leaving open whether it caps crossings or aggregated token rows; only 'recent' hints at recency ordering. Baseline 3 given partial schema coverage.

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 token crossings between Zenith EVM and Canton') plus the data provenance (decoded from Gateway contract events) and the aggregation shape (per-token counts by direction). An agent can distinguish this from a raw log or message-inbox tool, though no sibling is named 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: 'recent' plus 'per-token counts by direction' signals a monitoring/liveness summary rather than a per-crossing detail or lookup. There is no explicit when-to-use or when-not guidance, and no pointer to alternatives such as gateway_inbox or gateway_deposit_status for individual crossings.

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