Skip to main content
Glama

list_requests

View all user requests with their task summaries and status to track progress in the TaskFlow MCP task management system.

Instructions

List all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'list_requests' that delegates to the TaskFlowService.listRequests() method.
    async list_requests() {
      return service.listRequests();
    },
  • JSON Schema definition for the 'list_requests' tool input (empty object since no parameters).
    list_requests: {
      type: "object",
      properties: {},
      required: [],
    },
  • Registration of the 'list_requests' tool (as LIST_REQUESTS_TOOL) in the server's list of available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        PLAN_TASK_TOOL,
        GET_NEXT_TASK_TOOL,
        MARK_TASK_DONE_TOOL,
        OPEN_TASK_DETAILS_TOOL,
        LIST_REQUESTS_TOOL,
        ADD_TASKS_TO_REQUEST_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        ADD_SUBTASKS_TOOL,
        MARK_SUBTASK_DONE_TOOL,
        UPDATE_SUBTASK_TOOL,
        DELETE_SUBTASK_TOOL,
        EXPORT_TASK_STATUS_TOOL,
        ADD_NOTE_TOOL,
        UPDATE_NOTE_TOOL,
        DELETE_NOTE_TOOL,
        ADD_DEPENDENCY_TOOL,
        GET_PROMPTS_TOOL,
        SET_PROMPTS_TOOL,
        UPDATE_PROMPTS_TOOL,
        REMOVE_PROMPTS_TOOL,
        ARCHIVE_COMPLETED_REQUESTS_TOOL,
        LIST_ARCHIVED_REQUESTS_TOOL,
        RESTORE_ARCHIVED_REQUEST_TOOL,
      ],
    }));
  • Core service method that loads task data and formats the list of all requests with summary statistics.
    public async listRequests() {
      await this.loadTasks();
      const requestsList = formatRequestsList(this.data);
      return {
        status: "requests_listed",
        message: `Current requests in the system:\n${requestsList}`,
        requests: this.data.requests.map((req) => ({
          requestId: req.requestId,
          originalRequest: req.originalRequest,
          totalTasks: req.tasks.length,
          completedTasks: req.tasks.filter((t) => t.done).length,
        })),
      };
    }
  • Tool object definition for 'list_requests', exported and imported for server registration.
    export const LIST_REQUESTS_TOOL: Tool = {
      name: "list_requests",
      description:
        "List all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
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. It mentions the tool lists 'basic information and summary of tasks' but doesn't disclose key behavioral traits: whether it's paginated, sorted, filtered, or if it requires specific permissions. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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 two sentences, front-loaded with the core purpose and followed by a clarifying context sentence. Every word earns its place, with no redundancy or fluff. It's appropriately sized for a simple list tool.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior (e.g., pagination, sorting) and output format. For a list tool with no structured output documentation, this leaves gaps in completeness.

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% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but that's appropriate here. A baseline of 4 is applied since there are no parameters to document, and the description doesn't introduce unnecessary complexity.

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 tool's purpose: 'List all requests with their basic information and summary of tasks.' It specifies the verb ('List') and resource ('requests'), and distinguishes it from siblings like 'list_archived_requests' by implying it lists active/non-archived requests. However, it doesn't explicitly contrast with 'list_archived_requests', so it's not a perfect 5.

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

Usage Guidelines3/5

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

The description implies usage context: 'provides a quick overview of all requests in the system' suggests this is for high-level scanning rather than detailed inspection. However, it doesn't explicitly state when to use this tool versus alternatives like 'list_archived_requests' or 'open_task_details', nor does it mention any prerequisites or exclusions, leaving room for ambiguity.

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/pinkpixel-dev/taskflow-mcp'

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