Skip to main content
Glama
unctad-ai

eRegulations MCP Server

by unctad-ai

getProcedureStep

Retrieve specific step details from a procedure using procedure and step IDs. Enables AI systems to access structured eRegulations data for accurate administrative procedure queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
procedureIdYesID of the procedure
stepIdYesID of the step within the procedure

Implementation Reference

  • The main handler function createGetProcedureStepHandler that implements the tool logic: validates args, calls the API to get the step, formats it using formatters.step.format, and returns formatted text content or error.
    export function createGetProcedureStepHandler(
      api: ERegulationsApi
    ): ToolHandler {
      return {
        name: ToolName.GET_PROCEDURE_STEP,
        description: `Get information about a specific step within a procedure.`,
        inputSchema: zodToJsonSchema(GetProcedureStepSchema),
        inputSchemaDefinition: GetProcedureStepSchema,
        handler: async (args: any) => {
          try {
            // Use the inferred type for args
            const { procedureId, stepId } = args as GetProcedureStepArgs;
    
            logger.log(
              `Handling GET_PROCEDURE_STEP request for procedure ${procedureId}, step ${stepId}`
            );
    
            const step = await api.getProcedureStep(procedureId, stepId);
    
            // Use the step formatter - get result (data part ignored)
            const formattedResult = formatters.step.format(step);
    
            logger.log(`GET_PROCEDURE_STEP returning step ${step.name}`);
    
            // Always return only text content
            return {
              content: [
                {
                  type: "text",
                  text: formattedResult.text,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error retrieving step details: ${
                    error instanceof Error ? error.message : String(error)
                  }`,
                },
              ],
            };
          }
        },
      };
    }
  • Zod schema for input validation of getProcedureStep tool, requiring procedureId and stepId as numbers.
    export const GetProcedureStepSchema = z.object({
      procedureId: z.number().describe("ID of the procedure"),
      stepId: z.number().describe("ID of the step within the procedure"),
    });
  • Registration of the getProcedureStep handler within the createHandlers factory function that returns all tool handlers.
    export function createHandlers(api: ERegulationsApi): ToolHandler[] {
      return [
        createListProceduresHandler(api),
        createGetProcedureDetailsHandler(api),
        createGetProcedureStepHandler(api),
        createSearchProceduresHandler(api),
      ];
    }
  • Supporting API method in ERegulationsApi class that fetches the specific procedure step from the backend API endpoint.
    async getProcedureStep(procedureId: number, stepId: number): Promise<Step> {
      if (!procedureId || procedureId <= 0) {
        throw new Error("Procedure ID is required");
      }
      if (!stepId || stepId <= 0) {
        throw new Error("Step ID is required");
      }
      return this.fetchData<Step>(async () => {
        logger.log(`Fetching step ${stepId} for procedure ${procedureId}...`);
    
        // Access baseUrl at execution time
        const baseUrl = this.getBaseUrl();
    
        // Use the dedicated step endpoint to get complete step information
        interface StepResponse {
          data?: Step;
          links?: ApiLink[];
        }
    
        const response = await this.makeRequest<StepResponse>(
          `${baseUrl}/Procedures/${procedureId}/Steps/${stepId}`
        );
    
        if (!response || !response.data) {
          throw new Error(
            `Failed to get step ${stepId} for procedure ${procedureId}`
          );
        }
    
        const stepData = response.data;
    
        // Add additional context to the step data
        return {
          id: stepId,
          name: "Unknown", // Default value if step data is incomplete
          ...(stepData.data || {}),
          procedureId,
          _links: stepData.links,
        };
      });
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/unctad-ai/eregulations-mcp-server'

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