Agent Margin Router

Contract Info

contract_info

Read-only

Smart-contract metadata from Blockscout for Base, Ethereum, Optimism or Arbitrum: verification status, name, compiler, proxy/implementation, creator, creation tx, token details and function/event names. Pay per call with USDC or USDT on Base via x402. 3 free calls per wallet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Chain (default base).	base
`wallet`	No	Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet).
`address`	Yes	EVM contract or wallet address (0x...).
`api_key`	No	Optional AMR enterprise API key.
`x_payment`	No	Optional signed x402 payment payload (base64 JSON) for USDC/USDT on Base.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`token`	No	Token actually used for payment (USDC, USDT or FREE).	USDC
`source`	Yes
`address`	Yes
`routing`	Yes	How the request was routed (provider, fallback, cache, latency).
`is_proxy`	No
`language`	No
`cost_usdc`	Yes	Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.
`fetched_at`	No	UTC timestamp when the data was fetched.
`proxy_type`	No
`token_info`	No
`event_names`	No
`is_contract`	Yes
`is_verified`	No
`verified_at`	No
`explorer_url`	No
`license_type`	No
`abi_available`	No
`contract_name`	No
`function_names`	No
`creator_address`	No
`implementations`	No
`compiler_version`	No
`creation_tx_hash`	No
`freshness_seconds`	Yes	Age of the underlying data in seconds (0 = fetched live).
`x_payment_response`	No	Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.
`optimization_enabled`	No
`source_code_available`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response for ``POST /contract-info``.",
+  "properties": {
+    "abi_available": {
+      "default": false,
+      "title": "Abi Available",
+      "type": "boolean"
+    },
+    "address": {
+      "title": "Address",
+      "type": "string"
+    },
+    "chain": {
+      "title": "Chain",
+      "type": "string"
+    },
+    "compiler_version": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Compiler Version"
+    },
+    "contract_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Contract Name"
+    },
+    "cost_usdc": {
+      "description": "Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.",
+      "title": "Cost Usdc",
+      "type": "number"
+    },
+    "creation_tx_hash": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Creation Tx Hash"
+    },
+    "creator_address": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Creator Address"
+    },
+    "event_names": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Event Names",
+      "type": "array"
+    },
+    "explorer_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Explorer Url"
+    },
+    "fetched_at": {
+      "description": "UTC timestamp when the data was fetched.",
+      "format": "date-time",
+      "title": "Fetched At",
+      "type": "string"
+    },
+    "freshness_seconds": {
+      "description": "Age of the underlying data in seconds (0 = fetched live).",
+      "title": "Freshness Seconds",
+      "type": "integer"
+    },
+    "function_names": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Function Names",
+      "type": "array"
+    },
+    "implementations": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Implementations",
+      "type": "array"
+    },
+    "is_contract": {
+      "title": "Is Contract",
+      "type": "boolean"
+    },
+    "is_proxy": {
+      "default": false,
+      "title": "Is Proxy",
+      "type": "boolean"
+    },
+    "is_verified": {
+      "default": false,
+      "title": "Is Verified",
+      "type": "boolean"
+    },
+    "language": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Language"
+    },
+    "license_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "License Type"
+    },
+    "optimization_enabled": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Optimization Enabled"
+    },
+    "proxy_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Proxy Type"
+    },
+    "routing": {
+      "description": "How the request was routed (provider, fallback, cache, latency).",
+      "properties": {
+        "cache_hit": {
+          "default": false,
+          "description": "True if the result was served from cache.",
+          "title": "Cache Hit",
+          "type": "boolean"
+        },
+        "fallback_used": {
+          "default": false,
+          "description": "True if the primary provider failed and a fallback served the result.",
+          "title": "Fallback Used",
+          "type": "boolean"
+        },
+        "latency_ms": {
+          "default": 0,
+          "description": "End-to-end routing latency in milliseconds.",
+          "title": "Latency Ms",
+          "type": "integer"
+        },
+        "provider": {
+          "description": "Name of the upstream provider that served the result.",
+          "title": "Provider",
+          "type": "string"
+        },
+        "providers_tried": {
+          "description": "Providers attempted, in order.",
+          "items": {
+            "type": "string"
+          },
+          "title": "Providers Tried",
+          "type": "array"
+        }
+      },
+      "required": [
+        "provider"
+      ],
+      "title": "RoutingMeta",
+      "type": "object"
+    },
+    "source": {
+      "title": "Source",
+      "type": "string"
+    },
+    "source_code_available": {
+      "default": false,
+      "title": "Source Code Available",
+      "type": "boolean"
+    },
+    "token": {
+      "default": "USDC",
+      "description": "Token actually used for payment (USDC, USDT or FREE).",
+      "title": "Token",
+      "type": "string"
+    },
+    "token_info": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Token Info"
+    },
+    "verified_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Verified At"
+    },
+    "x_payment_response": {
+      "description": "Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "freshness_seconds",
+    "cost_usdc",
+    "routing",
+    "address",
+    "chain",
+    "is_contract",
+    "source"
+  ],
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, lowering the burden on the description. The description adds useful behavioral context: data source (Blockscout), supported chains, the pay-per-call model via x402, and the 3-free-calls per wallet. No contradiction with annotations exists.

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 compact sentences capture the core purpose and the payment model. The first sentence front-loads the metadata categories and supported chains; the second adds essential usage cost information. There is no filler or redundant restatement.

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 rich schema coverage, annotations, and an output schema present, the description does not need to explain return values. It provides enough context around chains, metadata scope, and payment requirements for an agent to call the tool correctly. Minor gaps such as explicit error/cost edge cases are acceptable given the annotations.

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 description coverage is 100%, so the schema already documents each parameter, including the wallet unlock behavior and the x_payment payload format. The description reinforces the payment context but does not add significant new parameter-level 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?

The description clearly identifies the tool's resource ('Smart-contract metadata from Blockscout') and lists concrete output categories like verification status, compiler, proxy/implementation, and token details. It does not use an explicit verb like 'get' or 'fetch', but the domain and supported chains are specific enough to distinguish it from sibling tools such as erc20_balance or tx_status.

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 implies the use case: query contract metadata for a given address on one of four chains. However, it does not explicitly state when to prefer this tool over alternatives, such as erc20_balance or token_price, nor does it define exclusions. The payment and free-tier notes provide context but not alternative routing.

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

All Agent Margin Router tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.