Skip to main content
Glama
Alubiama

Aerodrome MCP for Base

by Alubiama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read a saved wallet change report

aerodrome_wallet_report
Read-onlyIdempotent

Retrieve a committed wallet change report by its ID. Access saved report data without RPC or baseline changes, even during another capture.

Instructions

Retrieve a committed report by reportId (the original requestId) within the configured wallet scope. No RPC, capture or baseline change. Available after restart and while another capture is running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
chainIdYes
changesYes
findingsYes
reportIdYes
warningsYes
observationYes
reportSavedYes
epochChangedYes
baselineSavedYes
blockchainReadOnlyYes
initializedSectionsNo
previousObservationYes
unavailableSectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • changedOutput schema / properties / changes / items / properties / section / enum
      Previous value: -[
-  "protocol",
-  "voting",
-  "rewards"
-]New value: +[
+  "protocol",
+  "voting",
+  "rewards",
+  "balances",
+  "locks"
+]
    • addedOutput schema / properties / findings
      Added value: +{
+  "default": [],
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "enum": [
+          "BASELINE_CREATED",
+          "SECTION_UNAVAILABLE",
+          "EPOCH_CHANGED",
+          "OWNER_CHANGED",
+          "VOTING_POWER_CHANGED",
+          "REWARD_CHANGED",
+          "ROW_APPEARED",
+          "ROW_NO_LONGER_OBSERVED",
+          "VALUE_CHANGED",
+          "SECTION_BASELINE_CREATED",
+          "BALANCE_CHANGED",
+          "LOCK_CHANGED"
+        ],
+        "type": "string"
+      },
+      "decimals": {
+        "anyOf": [
+          {
+            "maximum": 36,
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deltaFormatted": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fromBlock": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "key": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "level": {
+        "enum": [
+          "INFO",
+          "ATTENTION"
+        ],
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "section": {
+        "enum": [
+          "protocol",
+          "voting",
+          "rewards",
+          "balances",
+          "locks"
+        ],
+        "type": "string"
+      },
+      "sources": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "toBlock": {
+        "type": "string"
+      },
+      "token": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "code",
+      "level",
+      "section",
+      "key",
+      "message",
+      "fromBlock",
+      "toBlock",
+      "token",
+      "decimals",
+      "deltaFormatted",
+      "sources"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / initializedSections
      Added value: +{
+  "items": {
+    "enum": [
+      "balances",
+      "locks"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / unavailableSections / items / enum
      Previous value: -[
-  "voting",
-  "rewards"
-]New value: +[
+  "voting",
+  "rewards",
+  "balances",
+  "locks"
+]
    • changedOutput schema / required
      Previous value: -[
-  "status",
-  "chainId",
-  "blockchainReadOnly",
-  "observation",
-  "previousObservation",
-  "reportId",
-  "reportSaved",
-  "baselineSaved",
-  "epochChanged",
-  "changes",
-  "unavailableSections",
-  "warnings"
-]New value: +[
+  "status",
+  "chainId",
+  "blockchainReadOnly",
+  "observation",
+  "previousObservation",
+  "reportId",
+  "reportSaved",
+  "baselineSaved",
+  "epochChanged",
+  "changes",
+  "findings",
+  "unavailableSections",
+  "warnings"
+]
  2. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds valuable context: it clarifies that the operation does not affect RPC, capture, or baseline, and that it is available even during captures and after restart. This goes beyond the annotations and helps an agent understand operational constraints.

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?

The description is two sentences, with the primary action front-loaded: 'Retrieve a committed report by reportId'. It then adds two concise clarifications (no side effects and availability) without redundancy. Every sentence earns its place, making it an efficiently structured description.

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 read tool with one parameter and an existing output schema, the description covers the essential operational aspects: it retrieves a committed report, is read-only, and is available under specific conditions. It does not mention error handling or return format, but the output schema presumably covers that. The description is sufficiently complete for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explicitly explains that reportId is the original requestId, which is a meaningful semantic clarification beyond the raw schema. While it does not detail the UUID format (already in the pattern), this mapping is crucial for correct usage, giving the description significant added value.

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?

The description clearly states the tool retrieves a committed report by reportId, with the specific resource being a saved wallet change report. It distinguishes itself from sibling tools by focusing on reading a previously saved report rather than creating or modifying data, though it does not explicitly name an alternative.

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?

The description provides context on when the tool is available (after restart and during another capture) and states it does not change RPC, capture, or baseline. However, it does not explicitly compare against sibling tools or specify scenarios where this tool is preferred over others, leaving some ambiguity for an agent deciding between tools.

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

Deploy Server

Other Tools