Skip to main content
Glama

make_app_clear_txn

Create an application clear state transaction on the Algorand blockchain to remove local state data from a smart contract application.

Instructions

Create an application clear state transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesSender address in standard Algorand format (58 characters)
appIndexYesID of the application to clear state 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?

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. It states this 'creates' a transaction but doesn't clarify whether this actually submits the transaction, what permissions are required, what the expected outcome is, or any side effects. The term 'clear state' is not explained, leaving the agent to guess at the tool's behavior.

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?

The description is extremely concise - a single sentence with no wasted words. However, this conciseness comes at the cost of being under-specified for a complex tool with 14 parameters. The structure is front-loaded but lacks necessary 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?

For a complex transaction creation tool with 14 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what the tool returns, what 'clear state' means operationally, when this transaction type is used, or how it differs from similar application transaction tools. The agent would struggle to use this tool correctly without significant external knowledge.

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?

The description provides no parameter information beyond what's already in the schema. With 100% schema description coverage, the baseline is 3. However, the description doesn't add any context about how parameters interact (e.g., that 'onComplete' should typically be 3 for clear state transactions, or how 'appArgs' might be used during clearing).

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 'Create an application clear state transaction' clearly states the action (create) and resource (application clear state transaction), but it's vague about what this operation actually does. It doesn't explain what 'clear state' means in the Algorand context or how this differs from similar tools like make_app_closeout_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 Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. With multiple sibling tools for application transactions (make_app_call_txn, make_app_closeout_txn, make_app_create_txn, etc.), the description offers no context about when this specific clear state transaction is appropriate versus other application transaction types.

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