Skip to main content
Glama

list_sips

Discover all available Stacks Improvement Proposals (SIPs) to identify blockchain standards for development compliance and implementation guidance.

Instructions

Get a list of all available SIPs (Stacks Improvement Proposals) in the knowledge base. Use this first to discover available Stacks standards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete tool definition including handler logic for 'list_sips', which fetches available SIPs, identifies those with Clarity code, formats a list, and returns it as text.
    server.addTool({
      name: "list_sips",
      description: "Get a list of all available SIPs (Stacks Improvement Proposals) in the knowledge base. Use this first to discover available Stacks standards.",
      parameters: z.object({}),
      execute: async () => {
        const sips = getAvailableSIPs();
        const sipsWithCode = getSIPsWithClarityCode();
        
        const list = sips.map((num) => {
          const hasCode = sipsWithCode.includes(num) ? " šŸ”„ (with Clarity code)" : "";
          return `- SIP-${num.padStart(3, "0")}${hasCode}`;
        }).join("\n");
        
        return {
          text: `Available SIPs:\n${list}\n\nšŸ”„ = Contains Clarity smart contract code\n\nUse get_sip with the SIP number to retrieve full content.\nKey standards: SIP-009 (NFT), SIP-010 (FT), SIP-012 (Performance)`,
          type: "text",
        };
      },
    });
  • Input schema for list_sips: no parameters required.
    parameters: z.object({}),
  • Helper function that scans the stacks-clarity-standards directory for sip-XXX directories and returns sorted array of SIP numbers.
    export const getAvailableSIPs = (): string[] => {
      try {
        const dirs = fs.readdirSync(stacksClarityStandardsDir);
        return dirs
          .filter((dir) => dir.startsWith("sip-"))
          .map((dir) => dir.replace("sip-", ""))
          .sort((a, b) => parseInt(a) - parseInt(b));
      } catch (err) {
        console.error(`Error reading SIPs directory: ${err}`);
        return [];
      }
    };
  • Helper function that identifies SIPs containing Clarity smart contract files (.clar) by scanning each SIP directory.
    export const getSIPsWithClarityCode = (): string[] => {
      const allSIPs = getAvailableSIPs();
      const sipsWithCode: string[] = [];
      
      for (const sipNum of allSIPs) {
        try {
          const sipDir = pathJoin(stacksClarityStandardsDir, `sip-${sipNum.padStart(3, "0")}`);
          if (fs.existsSync(sipDir)) {
            const files = fs.readdirSync(sipDir);
            const clarFiles = files.filter((file) => file.endsWith(".clar"));
            if (clarFiles.length > 0) {
              sipsWithCode.push(sipNum);
            }
          }
        } catch (error) {
          console.error(`Error checking SIP-${sipNum} for Clarity code:`, error);
        }
      }
      
      return sipsWithCode;
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool lists 'all available SIPs' and suggests using it for discovery, but doesn't disclose behavioral traits like whether it returns a complete list, pagination behavior, rate limits, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 two sentences, front-loaded with the core purpose followed by usage guidance. Every sentence earns its place: the first defines what the tool does, and the second explains when to use it. There's zero waste or redundancy.

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's simplicity (0 parameters, no output schema), the description is adequate but could be more complete. It covers purpose and basic usage, but without annotations or output schema, it doesn't describe what the return value looks like (e.g., format, structure) or other behavioral aspects. For a list operation, this is minimally viable but leaves room for improvement.

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%. The description doesn't need to add parameter information beyond what the schema provides (no parameters). It appropriately focuses on the tool's purpose and usage without unnecessary parameter details.

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 tool's purpose: 'Get a list of all available SIPs (Stacks Improvement Proposals) in the knowledge base.' It specifies the verb ('Get a list') and resource ('SIPs'), though it doesn't explicitly differentiate from sibling 'search_sips' beyond the 'all available' scope. The description avoids tautology by explaining what SIPs are.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'Use this first to discover available Stacks standards.' This gives a specific use case (initial discovery) but doesn't explicitly state when not to use it or mention alternatives like 'search_sips' for filtered searches. The guidance is helpful but could be more comprehensive.

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