Skip to main content
Glama

make_app_create_txn

Create an Algorand application creation transaction by specifying approval and clear programs, state parameters, and network details.

Instructions

Create an application creation transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesSender address in standard Algorand format (58 characters)
approvalProgramYesLogic that executes when the app is called (compiled TEAL as base64)
clearProgramYesLogic that executes when clear state is called (compiled TEAL as base64)
numGlobalByteSlicesYesNumber of byte array values in global state (0-64)
numGlobalIntsYesNumber of integer values in global state (0-64)
numLocalByteSlicesYesNumber of byte array values in local state per account (0-16)
numLocalIntsYesNumber of integer values in local state per account (0-16)
extraPagesNoAdditional program pages for larger programs (0-3)
noteNoTransaction note field (up to 1000 bytes)
leaseNoLease enforces mutual exclusion of transactions (32 bytes)
rekeyToNoAddress to rekey the sender account to
appArgsNoArguments to pass to the application (max 16 arguments)
accountsNoAccounts whose local state may be accessed (max 4 accounts)
foreignAppsNoIDs of apps whose global state may be accessed (max 8 apps)
foreignAssetsNoIDs of assets that may be accessed (max 8 assets)
feeNoTransaction fee in microAlgos. If not set, uses suggested fee from the network
flatFeeNoIf true, fee is used as-is (flat fee). If false (default), fee is per-byte
networkNoAlgorand network to use (default: mainnet)
itemsPerPageNoNumber of items per page for paginated responses (default: 10)
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but fails completely. It doesn't indicate whether this is a read-only or destructive operation, what permissions are required, whether it submits a transaction or just constructs one, what happens on success/failure, or any rate limits. The description merely restates the action without behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just one sentence, the description is under-specified rather than efficiently informative. It wastes its single sentence on a tautological restatement of the tool name instead of providing any useful context about the tool's purpose or behavior.

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

Completeness1/5

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

For a complex transaction construction tool with 19 parameters, no annotations, and no output schema, the description is completely inadequate. It should explain what kind of transaction is created, how it's used, what the expected output is, and critical behavioral aspects like whether it requires signing or network submission.

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%, providing detailed documentation for all 19 parameters. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline score of 3. However, it doesn't compensate for any gaps since there are none in the schema.

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

Purpose2/5

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

The description 'Create an application creation transaction' is a tautology that restates the tool name 'make_app_create_txn' without adding meaningful specificity. It doesn't clarify what an 'application creation transaction' entails in the Algorand context or how it differs from similar sibling tools like 'make_app_update_txn' or 'make_app_delete_txn'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for application transactions (e.g., make_app_update_txn, make_app_delete_txn), but the description offers no context about prerequisites, typical use cases, or when this specific creation tool is appropriate.

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/GoPlausible/algorand-mcp'

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