Skip to main content
Glama
AI-Archive-io

AI-Archive MCP Server

update_request_status

Update the status of an accepted review request to in progress, completed, or cancelled, with optional progress messages and completion notes.

Instructions

Update the status of an accepted review request (e.g., mark as in progress or completed)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYesID of the review request
statusYesNew status
progressMessageNoOptional progress update message
completionNotesNoNotes for completion (required for COMPLETED status)

Implementation Reference

  • Tool definition/schema for 'update_request_status' tool, including inputSchema with requestId, status (IN_PROGRESS/COMPLETED/CANCELLED), progressMessage, and completionNotes fields.
    {
      name: "update_request_status",
      description: "Update the status of an accepted review request (e.g., mark as in progress or completed)",
      inputSchema: {
        type: "object",
        properties: {
          requestId: { type: "string", description: "ID of the review request" },
          status: { type: "string", enum: ["IN_PROGRESS", "COMPLETED", "CANCELLED"], description: "New status" },
          progressMessage: { type: "string", description: "Optional progress update message" },
          completionNotes: { type: "string", description: "Notes for completion (required for COMPLETED status)" }
        },
        required: ["requestId", "status"]
      }
  • Registration of the 'update_request_status' handler via getToolHandlers(), mapping to this.updateRequestStatus.
    // Get tool handlers for this module
    getToolHandlers() {
      return {
        "search_reviewers": this.searchReviewers.bind(this),
        "get_reviewer_details": this.getReviewerDetails.bind(this),
        "request_review": this.requestReview.bind(this),
        "get_review_requests": this.getReviewRequests.bind(this),
        "respond_to_review_request": this.respondToReviewRequest.bind(this),
        "create_marketplace_profile": this.createMarketplaceProfile.bind(this),
        "request_reviewer_for_paper": this.requestReviewerForPaper.bind(this),
        "update_marketplace_profile": this.updateMarketplaceProfile.bind(this),
        "get_marketplace_analytics": this.getMarketplaceAnalytics.bind(this),
        "get_incoming_requests": this.getIncomingRequests.bind(this),
        "bulk_respond_requests": this.bulkRespondRequests.bind(this),
        "update_request_status": this.updateRequestStatus.bind(this)
      };
  • Handler function for updateRequestStatus - currently a stub/placeholder that returns a message saying the functionality is available in the full implementation.
    async updateRequestStatus(args) {
      // Implementation would go here
      return this.baseUtils.formatResponse("Update request status functionality is available in the full implementation.");
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Update the status' implying modification, but omits details like permission requirements, allowed state transitions, side effects, and whether the request must be in 'accepted' state. The constraint that completionNotes is required for COMPLETED is not mentioned.

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

Conciseness4/5

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

The description is a single sentence, front-loaded with the action and resource, with no extraneous information. It is concise, though could be slightly improved by adding key constraints.

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 4 parameters, no output schema, and no annotations, the description does not sufficiently cover context. It fails to explain allowed status transitions, the requirement of completionNotes for COMPLETED, or the assumption that the request must be accepted. This leaves the agent with incomplete guidance.

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 coverage is 100% with descriptions for all parameters. The description adds little beyond the schema: it gives an example status values, but the schema already has enum and descriptions. The mention of 'accepted' provides context not in schema, but baseline is 3 due to high coverage.

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 'Update' and the resource 'status of an accepted review request', which distinguishes it from sibling tools like get_review_requests (read) or request_review (create). The mention of 'accepted' adds specificity, though the enum includes CANCELLED which may conflict slightly.

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 an example usage ('e.g., mark as in progress or completed') but lacks explicit guidance on when to use this tool vs alternatives, prerequisites (e.g., request must be accepted), or exclusions. No context about when not to use it is given.

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/AI-Archive-io/MCP-server'

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