address_transactionsGet list of 20 MOST RECENT transactions made by an address (per page). Only the latest transactions according to the date range are returned.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / request / anyOfPrevious value: -[
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "description": "Complete request for address transactions (flattened).",
- "properties": {
- "address": {
- "description": "Single address to analyze",
- "type": "string"
- },
- "chain": {
- "default": "evm",
- "type": "string"
- },
- "hideSpamToken": {
- "default": true,
- "description": "Remove suspicious tokens from transaction list",
- "type": "boolean"
- },
- "page": {
- "default": 1,
- "type": "integer"
- }
- },
- "required": [
- "address"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "description": "Complete request for address transactions (flattened).",
+ "properties": {
+ "address": {
+ "description": "Single address to analyze",
+ "type": "string"
+ },
+ "chain": {
+ "default": "evm",
+ "type": "string"
+ },
+ "dateRange": {
+ "description": "Date range for transactions (defaults to last 30 days)",
+ "properties": {
+ "from": {
+ "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+ "type": "string"
+ },
+ "to": {
+ "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+ "type": "string"
+ }
+ },
+ "required": [
+ "from",
+ "to"
+ ],
+ "type": "object"
+ },
+ "hideSpamToken": {
+ "default": true,
+ "description": "Remove suspicious tokens from transaction list",
+ "type": "boolean"
+ },
+ "page": {
+ "default": 1,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "address"
+ ],
+ "type": "object"
+ }
+]Input schema / $defsRemoved value: -{
- "AddressTransactionsRequest": {
- "description": "Complete request for address transactions (flattened).",
- "properties": {
- "address": {
- "description": "Single address to analyze",
- "type": "string"
- },
- "chain": {
- "default": "evm",
- "type": "string"
- },
- "hideSpamToken": {
- "default": true,
- "description": "Remove suspicious tokens from transaction list",
- "type": "boolean"
- },
- "page": {
- "default": 1,
- "type": "integer"
- }
- },
- "required": [
- "address"
- ],
- "type": "object"
- }
-}Input schema / additionalPropertiesAdded value: +falseInput schema / properties / request / anyOfPrevious value: -[
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "$ref": "#/$defs/AddressTransactionsRequest"
- }
-]New value: +[
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "description": "Complete request for address transactions (flattened).",
+ "properties": {
+ "address": {
+ "description": "Single address to analyze",
+ "type": "string"
+ },
+ "chain": {
+ "default": "evm",
+ "type": "string"
+ },
+ "hideSpamToken": {
+ "default": true,
+ "description": "Remove suspicious tokens from transaction list",
+ "type": "boolean"
+ },
+ "page": {
+ "default": 1,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "address"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral details like the 20-per-page limit and date-range ordering, though it does not describe edge cases or pagination behavior beyond this.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler. The most important facts—recency, limit, and date-range behavior—are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description, together with the annotations and output schema, covers the core behavior of the tool. Some parameter-level details are left to the schema, but existing structured info and output schema reduce the burden on the description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description should compensate for explaining parameters. It only generically references 'per page' and 'date range', leaving address, chain, page, dateRange formatting, and hideSpamToken mostly unexplained at the description level.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Get list of 20 MOST RECENT transactions') and a clear resource ('made by an address'), with explicit pagination ('per page'). This distinguishes it from sibling tools like address_dex_trades and transaction_lookup at a high level.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: this tool returns the most recent address transactions within a date range, paginated. It does not explicitly name alternatives or exclusions, but the use case is evident from the wording.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.