Skip to main content
Glama
Seitrace

Seitrace Insights MCP Server

Official
by Seitrace

list_resource_actions

Retrieve all available actions for a specified resource using the Seitrace Insights MCP Server. This tool enables efficient access to blockchain data by listing actions associated with a given resource name.

Instructions

List actions for a given resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYesResource name.

Implementation Reference

  • The primary handler function for the 'list_resource_actions' tool. It resolves the topic from the resource name, validates the resource exists, and delegates to the topic's listResourceActions method.
    export const listResourceActionsHandler = async (toolArgs: ToolArgs): Promise<CallToolResult> => {
      const { resource } = toolArgs;
      const topicKey = resource.split('_')[0];
      const foundResource = TOPIC_KEY_MAP[topicKey] || TOPIC_KEY_MAP[resource];
    
      /**
       * Check if the resource exists
       */
      if (!foundResource || !(await foundResource.getResources()).has(resource)) {
        return McpResponse(JSON.stringify({ error: `Unknown or missing resource '${resource}'.` }));
      }
    
      /**
       * List actions for the resource
       */
      return foundResource.listResourceActions(toolArgs);
    };
  • The Tool object definition including name, description, and inputSchema for the 'list_resource_actions' tool, used in tool listing.
    const listResourceActions: Tool = {
      name: LIST_RESOURCE_ACTIONS_TOOL,
      description:
        'List available actions for a given resource (step 2). Each action will show a brief description, but you MUST use get_resource_action_schema to see the exact parameter requirements before invoking.',
      inputSchema: {
        type: 'object',
        properties: {
          resource: { type: 'string', description: 'Resource name from list_resources output.' },
        },
        required: ['resource'],
        additionalProperties: false,
        description: 'Provide the resource name.',
      },
    };
  • Registers the listResourceActionsHandler for the LIST_RESOURCE_ACTIONS_TOOL name in the central handlerMap.
    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,
    };
  • Imports the listResourceActionsHandler for registration.
    import { listResourceActionsHandler } from './list_resource_actions.js';
  • Defines the constant string name for the 'list_resource_actions' tool.
    export const LIST_RESOURCE_ACTIONS_TOOL = 'list_resource_actions';
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 of behavioral disclosure. It states 'List actions' but doesn't describe what an 'action' entails (e.g., operations, permissions, or workflows), how results are returned (e.g., pagination, format), or any limitations (e.g., rate limits, authentication needs). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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: 'List actions for a given resource.' It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool. Every part of the sentence contributes directly to understanding the tool's function.

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 lack of annotations and output schema, the description is incomplete for a tool that lists actions. It doesn't explain what 'actions' are, how they're structured, or what the return value looks like. For a tool with 1 parameter and no structured output information, more context is needed to fully understand its operation and results.

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 description coverage is 100%, with the parameter 'resource' documented as 'Resource name.' in the schema. The description adds no additional meaning beyond this, such as examples of valid resource names or how they relate to actions. Since the schema already provides basic documentation, the baseline score of 3 is appropriate, but no extra value is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List actions for a given resource' clearly states the verb ('List') and resource ('actions'), but it's vague about what 'actions' means in this context. It doesn't distinguish from siblings like 'list_resources' (which lists resources rather than actions) or 'get_resource_action_schema' (which gets schema details rather than listing). The purpose is understandable but lacks specificity about the nature of these actions.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for selecting this over siblings like 'list_resources' or 'invoke_resource_action', or any constraints. Without such information, the agent must infer usage from tool names alone, which is insufficient for optimal selection.

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