Skip to main content
Glama
Seitrace

Seitrace Insights MCP Server

Official
by Seitrace

list_resources

Retrieve available blockchain data resources (ERC-20, ERC-721, native tokens) on the Seitrace Insights MCP Server to query specific on-chain insights and information.

Instructions

List available resources (e.g., insights_erc20, insights_erc721, insights_native).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main execution logic for the list_resources tool. Aggregates resources from all topics using AVAILABLE_TOPICS, generates LLM-friendly descriptions using RESOURCE_DESCRIPTION_MAP or action names, sorts them, and returns as MCP response.
    export const listResourcesHandler = async (_: ToolArgs): Promise<CallToolResult> => {
      /**
       * List all available resources.
       */
      const allResources = await Promise.all(
        AVAILABLE_TOPICS.map(async (topic) => {
          return await topic.getResources();
        })
      );
    
      /**
       * Build an enriched list of resources with short, LLM-friendly descriptions.
       * Description strategy:
       * - Provide a concise action summary (comma-separated action names).
       * - For well-known resources, use more direct phrasing.
       */
      const resources = allResources
        .reduce<{ name: string; description: string }[]>((acc, topicResources) => {
          for (const [name, grouped] of topicResources.entries()) {
            const actionNames = Object.keys(grouped.actions).sort();
            let description: string = '';
    
            description = RESOURCE_DESCRIPTION_MAP[name];
    
            if (!description) {
              // Generic, context-optimized fallback using action names
              const preview = actionNames.slice(0, 6).join(', ');
              const suffix = actionNames.length > 6 ? ', …' : '';
              description = `Actions: ${preview}${suffix}.`;
            }
    
            acc.push({ name, description });
          }
          return acc;
        }, [])
        // Ensure stable ordering
        .sort((a, b) => a.name.localeCompare(b.name));
    
      // Return the list of resources.
      return McpResponse(JSON.stringify({ resources }));
    };
  • Defines the input schema and metadata for the list_resources tool as part of the tools list. No input parameters required.
    const listResource: Tool = {
      name: LIST_RESOURCES_TOOL,
      description:
        'List available resources for Sei blockchain analysis (e.g., insights_erc20, insights_erc721, insights_native, insights_erc1155, smart_contract, general). This is the first step - start here to discover available resources.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
        additionalProperties: false,
        description: 'No arguments required.',
      },
    };
  • Registers list_resources handler by mapping the tool name to listResourcesHandler function in the central handlerMap used by MCP servers.
    export const handlerMap = {
      [LIST_RESOURCES_TOOL]: listResourcesHandler,
      [LIST_RESOURCE_ACTIONS_TOOL]: listResourceActionsHandler,
      [GET_RESOURCE_ACTION_SCHEMA_TOOL]: getResourceActionSchemaHandler,
      [GET_RESOURCE_ACTION_SNIPPET_TOOL]: getResourceActionSnippetHandler,
      [INVOKE_RESOURCE_ACTION_TOOL]: invokeResourceActionHandler,
    };
  • src/constants.ts:20-20 (registration)
    Defines the canonical string name for the list_resources tool, used in schema and handler registrations.
    export const LIST_RESOURCES_TOOL = 'list_resources';
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 for behavioral disclosure. The description only states what the tool does at a high level ('List available resources') but provides no information about what the listing returns (format, structure, completeness), whether there are limitations (pagination, rate limits), or what permissions might be required. For a tool with zero annotation coverage, this is insufficient 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, efficient sentence that gets straight to the point. The parenthetical examples are well-placed and add useful context without unnecessary elaboration. There's zero wasted space - every word serves a purpose in clarifying what the tool does.

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?

For a zero-parameter listing tool with no output schema, the description provides adequate basic information about what the tool does. However, it lacks important context about what the listing returns (format, structure) and how it relates to sibling tools. The examples help, but without annotations or output schema, more behavioral detail would be beneficial for a complete understanding.

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 input schema has 0 parameters with 100% description coverage, so the schema already fully documents that no arguments are required. The description appropriately doesn't waste space discussing parameters that don't exist. The examples provided ('insights_erc20, insights_erc721, insights_native') give helpful context about what types of resources might be listed, which adds value beyond the empty parameter schema.

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 ('List') and resource ('available resources'), and provides concrete examples of what types of resources might be listed. However, it doesn't explicitly differentiate from sibling tools like 'list_resource_actions' - both involve listing, so the distinction between 'resources' and 'resource actions' could be clearer.

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. With sibling tools like 'list_resource_actions' that also perform listing operations, there's no indication of when this tool is appropriate versus when other listing tools should be used. No prerequisites, exclusions, or alternative recommendations 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

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/Seitrace/seitrace-mcp'

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