Skip to main content
Glama

make_app_closeout_txn

Create a transaction to close out from an Algorand smart contract application, specifying sender address and application ID.

Instructions

Create an application close out transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesSender address in standard Algorand format (58 characters)
appIndexYesID of the application to close out from
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)
onCompleteNoApplication call completion behavior (0=NoOp, 1=OptIn, 2=CloseOut, 3=ClearState, 4=UpdateApplication, 5=DeleteApplication)
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)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Create' but doesn't disclose behavioral traits such as whether this is a mutating operation, if it requires specific permissions, potential side effects (e.g., affecting application state), or error conditions. This leaves critical gaps for a tool that likely modifies blockchain state.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to scan and understand quickly without unnecessary elaboration.

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

Completeness2/5

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

Given the complexity (14 parameters, no annotations, no output schema), the description is incomplete. It lacks context on what the tool returns (e.g., a transaction object), error handling, or how it fits into broader workflows (e.g., signing and sending the transaction). For a mutating blockchain tool, this leaves significant gaps for an agent.

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 fully documents all 14 parameters. The description adds no additional meaning beyond the schema, such as explaining how parameters interact (e.g., 'onComplete' defaulting to 2 for close-out) or providing examples. The baseline score of 3 reflects adequate parameter documentation solely from the schema.

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

Purpose3/5

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

The description states the action ('Create') and resource ('application close out transaction'), which clarifies the basic purpose. However, it's vague about what 'close out' means in the Algorand context (e.g., ending participation in a smart contract) and doesn't differentiate from sibling tools like 'make_app_clear_txn' or 'make_app_delete_txn', which might have overlapping or related functions.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing application), exclusions, or compare it to siblings like 'make_app_clear_txn' or 'make_app_delete_txn', leaving the agent to infer usage from context alone.

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