Skip to main content
Glama
armorwallet
by armorwallet

get_armor_mcp_version

Retrieve the current Armor Wallet version for blockchain operations, bridging, swapping, and AI agent trading strategies on the Armor Crypto MCP server.

Instructions

Get the current Armor Wallet version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_armor_mcp_version' tool. It is decorated with @mcp.tool() which also registers it with the MCP server. Simply returns a dictionary with the package version from __version__.
    @mcp.tool()
    async def get_armor_mcp_version():
        """Get the current Armor Wallet version"""
        return {'armor_version': __version__}
  • The package version constant referenced and returned by the get_armor_mcp_version tool.
    __version__ = "0.2.1"
  • The @mcp.tool() decorator registers this function as a tool named 'get_armor_mcp_version' with the FastMCP server.
    @mcp.tool()
    async def get_armor_mcp_version():
        """Get the current Armor Wallet version"""
        return {'armor_version': __version__}
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, or what the return format looks like (e.g., version string, object).

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 tool's simplicity (0 parameters, no output schema), the description is minimal but adequate for basic understanding. However, it lacks context about what 'version' entails (e.g., software version, API version) and doesn't compensate for missing annotations, leaving behavioral aspects unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here, warranting a baseline score above minimum viable.

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 verb 'Get' and the resource 'current Armor Wallet version', making the purpose specific and understandable. It doesn't distinguish from siblings, but since this is the only version-checking tool among the siblings, differentiation isn't critical here.

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. It doesn't mention prerequisites, timing, or context for invoking it, leaving the agent to infer usage based on 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.

Install Server

Other Tools

Related 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/armorwallet/armor-crypto-mcp'

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