Skip to main content
Glama

portal_evm_get_contract_deployment

Locate the deployer, deployment block, and transaction for any EVM contract using a block range, timestamp, or contract alias.

Instructions

Locate the create trace and parent transaction that deployed a specific EVM contract address within a bounded window.

COMMON USER ASKS:

  • Find BAYC deployment

  • Find recent deployment

  • Find deployment from known range

FIRST CHOICE FOR:

  • who deployed this EVM contract

  • when was this contract deployed

  • what deployment transaction created this contract

WHEN TO USE:

  • You need the deployer, deployment block, deployment timestamp, or deployment transaction for an EVM contract.

  • You can provide a starting block/time window, a contract address, or a supported well-known contract alias such as BAYC/Bored Apes.

  • You want a deployment lookup instead of general contract activity.

DON'T USE:

  • You need all activity for a contract after deployment.

  • The contract is old and no block/time hint is available; provide from_block or from_timestamp first.

EXAMPLES:

  • Find BAYC deployment: {"network":"ethereum-mainnet","contract":"bored apes","from_block":12000000,"to_block":13000000,"scan_order":"earliest"}

  • Find recent deployment: {"network":"base-mainnet","contract_address":"0xabc...","search_depth_blocks":100000}

  • Find deployment from known range: {"network":"ethereum-mainnet","contract_address":"0xabc...","from_block":17000000,"to_block":17100000,"scan_order":"earliest"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesEVM network name or alias, e.g. base, ethereum, arbitrum.
contractNoContract address or a supported well-known alias/name, e.g. "bayc" or "bored apes" on Ethereum.
to_blockNoOptional ending block. Defaults to the indexed head.
timeframeNoOptional recent time window to search, e.g. "24h" or "7d".
from_blockNoOptional starting block. Provide this for older contracts when the deployment is not recent.
scan_orderNoScan latest first for recent deployments, or earliest first when you provide a historical from_block.latest
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "7d ago".
max_scan_blocksNoSafety cap for historical deployment scans. Default: scan the requested window up to 1,000,000 blocks.
contract_addressNoContract address whose deployment transaction should be located.
search_depth_blocksNoWhen no explicit range is given, search this many recent blocks backward from the indexed head.
Behavior4/5

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

No annotations provided, so description carries burden. It explains what the tool returns (deployer, deployment block, etc.) but does not disclose operational traits like idempotency or rate limits. The behavioral context is reasonable but incomplete.

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?

Description is well-structured with clear sections, bullet points, and examples. It is moderately long but every section adds value. Could be slightly more concise, but overall good.

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?

Given 11 parameters and no output schema or annotations, the description covers common asks, usage guidelines, and multiple examples. It is complete and self-contained for the tool's complexity.

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 coverage is 100%, baseline 3. Description adds value via examples showing parameter combinations and default behaviors (e.g., search_depth_blocks=100000), and clarifies the role of 'contract' vs 'contract_address'. This justifies a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Locate the create trace and parent transaction that deployed a specific EVM contract address within a bounded window.' It uses specific verb and resource, and distinguishes from sibling tools like portal_evm_get_contract_activity via DON'T USE guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sections for 'FIRST CHOICE FOR:', 'WHEN TO USE:', and 'DON'T USE:' provide clear context, including specific alternatives like 'use portal_evm_get_contract_activity' and conditions for when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/subsquid-labs/portal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server