UluAlgorandMCP

get_contract_role

Identify the protocol role of an Algorand application, such as amm-router, name-registry, or lending-pool, to understand its function in the ecosystem.

Instructions

Get the known protocol role for an Algorand application (e.g. amm-router, name-registry, lending-pool)

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": {
      "appId": "<appId>"
    },
    "name": "get_contract_role"
  }
}

Input Schema

Name	Required	Description	Default
`appId`	Yes	Application ID on Algorand

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only hints at the 'known' nature of the role but does not disclose whether the operation is read-only, what happens for unknown apps, or error handling. This is a significant gap.

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 sentence that is front-loaded with the action, and the examples are informative without adding unnecessary length. No wasted words.

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

Completeness4/5

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

Given that the tool is simple with one documented parameter and no output schema, the description gives a clear idea of purpose and plausible outputs via examples. However, it does not explicitly describe return format or behavior for unknown applications, which is a minor gap.

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 coverage is 100%, so the baseline is 3. The description adds no meaning beyond the schema's 'Application ID on Algorand'; the examples pertain to output values rather than parameter syntax or semantics.

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 the verb 'Get' and the resource 'known protocol role for an Algorand application', with concrete examples. This distinguishes it from sibling tools like get_protocols, which focus on protocols rather than application roles.

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

Usage Guidelines3/5

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

The description implies usage for retrieving an application's protocol role, but provides no explicit context, preconditions, or comparison with alternatives like identify_application. It is self-explanatory but lacks direct guidance.

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

Deploy Server