Skip to main content
Glama

update-status

Update the progress status of research sections like projectInfo or technicalFundamentals to planned, in_progress, or completed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection name to update (e.g., 'projectInfo', 'technicalFundamentals')
statusYesNew status for the section

Implementation Reference

  • Registration of the 'update-status' tool, including input schema and inline handler function that updates the status of a research plan section in storage.
    server.tool(
      "update-status",
      {
        section: z
          .string()
          .describe(
            "Section name to update (e.g., 'projectInfo', 'technicalFundamentals')"
          ),
        status: z
          .enum(["planned", "in_progress", "completed"])
          .describe("New status for the section"),
      },
      async ({
        section,
        status,
      }: {
        section: string;
        status: "planned" | "in_progress" | "completed";
      }) => {
        try {
          const researchPlan = storage.getSection("researchPlan");
          if (!researchPlan || !researchPlan[section]) {
            return {
              isError: true,
              content: [
                {
                  type: "text",
                  text: `Section '${section}' not found in research plan`,
                },
              ],
            };
          }
    
          const updatedSection = {
            ...researchPlan[section],
            status,
          };
    
          const updatedPlan = {
            ...researchPlan,
            [section]: updatedSection,
          };
    
          storage.updateSection("researchPlan", updatedPlan);
          storage.addLogEntry(`Updated status of ${section} to ${status}`);
    
          return {
            content: [
              {
                type: "text",
                text: `Updated status of '${section}' to '${status}'`,
              },
            ],
          };
        } catch (error) {
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: `Error updating status: ${error}`,
              },
            ],
          };
        }
      }
    );
  • The handler function for 'update-status' tool. It retrieves the research plan from storage, updates the specified section's status, saves the updated plan back to storage, logs the change, and returns a success message or error.
    async ({
      section,
      status,
    }: {
      section: string;
      status: "planned" | "in_progress" | "completed";
    }) => {
      try {
        const researchPlan = storage.getSection("researchPlan");
        if (!researchPlan || !researchPlan[section]) {
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: `Section '${section}' not found in research plan`,
              },
            ],
          };
        }
    
        const updatedSection = {
          ...researchPlan[section],
          status,
        };
    
        const updatedPlan = {
          ...researchPlan,
          [section]: updatedSection,
        };
    
        storage.updateSection("researchPlan", updatedPlan);
        storage.addLogEntry(`Updated status of ${section} to ${status}`);
    
        return {
          content: [
            {
              type: "text",
              text: `Updated status of '${section}' to '${status}'`,
            },
          ],
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Error updating status: ${error}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the 'update-status' tool: 'section' (string) and 'status' (enum: planned, in_progress, completed).
    {
      section: z
        .string()
        .describe(
          "Section name to update (e.g., 'projectInfo', 'technicalFundamentals')"
        ),
      status: z
        .enum(["planned", "in_progress", "completed"])
        .describe("New status for the section"),
    },
  • Intermediate registration function that calls registerResearchTools, which includes the 'update-status' tool registration.
    export function registerAllTools(
      server: McpServer,
      storage: ResearchStorage
    ): void {
      registerResearchTools(server, storage);
    }
  • src/server.ts:187-187 (registration)
    Final call to register all tools, including 'update-status', on the MCP server instance.
    registerAllTools(server, storage);
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

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/aaronjmars/web3-research-mcp'

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