Skip to main content
Glama

get_token_standards

Retrieve Stacks blockchain token standards including SIP-009 for NFTs and SIP-010 for fungible tokens with Clarity trait definitions and implementation guidance.

Instructions

Get the essential token standards for Stacks - SIP-009 (NFT) and SIP-010 (Fungible Token) complete with Clarity trait definitions and implementation guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:88-96 (registration)
    Registers the 'get_token_standards' tool with the FastMCP server. Includes name, description, schema (empty input: z.object({})), and inline handler that executes getTokenStandardSIPs() and formats the response.
    server.addTool({
      name: "get_token_standards",
      description: "Get the essential token standards for Stacks - SIP-009 (NFT) and SIP-010 (Fungible Token) complete with Clarity trait definitions and implementation guidance.",
      parameters: z.object({}),
      execute: async () => {
        const standards = await getTokenStandardSIPs();
        return { text: standards, type: "text" };
      },
    });
  • Core helper function that fetches SIP-009 (NFT) and SIP-010 (FT) content using getSIPContent and combines them into a single markdown document with header.
    export const getTokenStandardSIPs = async (): Promise<string> => {
      const nftStandard = await getSIPContent("009");
      const ftStandard = await getSIPContent("010");
      
      return `# TOKEN STANDARDS\n\n${nftStandard}\n\n${ftStandard}`;
    };
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 describes what content is returned but lacks behavioral details such as whether this is a read-only operation (implied by 'Get'), if there are rate limits, authentication requirements, or how the guidance is structured (e.g., examples, best practices). The description is functional but minimal on behavioral context.

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, well-structured sentence that efficiently conveys the tool's purpose and output without unnecessary words. It is front-loaded with the core action ('Get the essential token standards') and adds specific details (SIP types, Clarity traits, guidance) that earn their place.

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

Completeness3/5

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

Given the tool has 0 parameters, no annotations, and no output schema, the description provides basic completeness by stating what it returns. However, it lacks details on output format (e.g., structured data, text), behavioral traits, or error handling, which could be important for an AI agent to use it effectively in context with sibling tools.

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 with 100% schema description coverage, so no parameter documentation is needed. The description does not discuss parameters, which is appropriate. A baseline of 4 is applied since it compensates adequately for the lack of parameters by focusing on output content.

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 tool's purpose with specific verbs ('Get') and resources ('essential token standards for Stacks - SIP-009 (NFT) and SIP-010 (Fungible Token)'), including what content it provides ('Clarity trait definitions and implementation guidance'). It distinguishes itself from sibling tools like get_sip009_token_info or get_sip010_info by focusing on standards documentation rather than specific token data.

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 when needing token standards information ('essential token standards... with... guidance'), but does not explicitly state when to use this tool versus alternatives like get_sip (which might retrieve SIP documents) or generate_sip009_template (for creating contracts). No exclusions or prerequisites are mentioned.

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/exponentlabshq/stacks-clarity-mcp'

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