Skip to main content
Glama
Sign In
Algorand MCP

Algorand MCP

by GoPlausible
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

api_tinyman_get_asset_optin_quote

Calculate transaction details for adding a Tinyman pool token to an Algorand account. Specify asset ID and account address to generate opt-in quote.

Instructions

Get quote for opting into a Tinyman pool token

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assetId": "<assetId>",
      "initiatorAddr": "<initiatorAddr>"
    },
    "name": "api_tinyman_get_asset_optin_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesID of the pool token asset
initiatorAddrYesAddress of the account to opt in
networkNoAlgorand network to use (default: mainnet)
itemsPerPageNoNumber of items per page for paginated responses (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.1

TDQS

C2.9/5.0
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. It states this is a 'Get quote' operation, implying it's a read-only, non-destructive query. However, it doesn't clarify whether this requires authentication, has rate limits, returns structured quote data, or what format the quote takes. For a financial quoting tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a straightforward quoting tool and front-loads the essential information.

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 financial quoting tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the quote contains (e.g., fees, minimum amounts, transaction structure), whether the quote is actionable or informational, or how it relates to actual opt-in execution. The agent lacks critical context to understand the tool's output and proper application.

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 4 parameters. The description adds no additional parameter semantics beyond what's already in the schema - it doesn't explain relationships between parameters, provide examples, or clarify edge cases. This meets the baseline expectation when schema coverage is complete.

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 states the action ('Get quote') and target ('for opting into a Tinyman pool token'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its closest sibling 'api_tinyman_get_validator_optin_quote', which appears to serve a similar opt-in quoting function but for validators rather than pool tokens.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this tool is appropriate versus other opt-in or quoting tools, or what context would trigger its use. The agent must infer usage from the tool name alone.

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

Deploy Server

Other Tools