Skip to main content
Glama

read_project

Retrieve detailed project information and task statuses using the project ID from the taskqueue-mcp server.

Instructions

Read all information for a given project, by its ID, including its tasks' statuses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project to read (e.g., proj-1).

Implementation Reference

  • MCP tool handler/executor for 'read_project'. Validates the projectId input parameter and delegates execution to TaskManager.readProject(projectId), returning the raw result data.
    const readProjectToolExecutor: ToolExecutor = {
      name: "read_project",
      async execute(taskManager, args) {
        // 1. Argument Validation
        const projectId = validateProjectId(args.projectId);
    
        // 2. Core Logic Execution
        const resultData = await taskManager.readProject(projectId);
    
        // 3. Return raw success data
        return resultData;
      },
    };
    toolExecutorMap.set(readProjectToolExecutor.name, readProjectToolExecutor);
  • Tool schema definition for 'read_project', including name, description, and inputSchema requiring a 'projectId' string.
    const readProjectTool: Tool = {
      name: "read_project",
      description: "Read all information for a given project, by its ID, including its tasks' statuses.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "The ID of the project to read (e.g., proj-1).",
          },
        },
        required: ["projectId"],
      },
    };
  • MCP server registration for listing tools. Returns ALL_TOOLS array which includes the 'read_project' tool schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: ALL_TOOLS
      };
    });
  • Core helper method implementing project reading logic. Finds the project by ID, returns structured data or throws if not found.
    public async readProject(projectId: string): Promise<ReadProjectSuccessData> {
      await this.ensureInitialized();
      await this.reloadFromDisk();
    
      const project = this.data.projects.find((p) => p.projectId === projectId);
      if (!project) {
        throw new AppError(`Project ${projectId} not found`, AppErrorCode.ProjectNotFound);
      }
    
      return {
        projectId: project.projectId,
        initialPrompt: project.initialPrompt,
        projectPlan: project.projectPlan,
        completed: project.completed,
        autoApprove: project.autoApprove,
        tasks: project.tasks,
      };
    }
  • MCP server registration for calling tools. Dispatches to executeToolAndHandleErrors which uses toolExecutorMap to invoke the 'read_project' handler.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      // Directly call the handler. It either returns a result object (success or isError:true)
      // OR it throws a tagged protocol error.
      return await executeToolAndHandleErrors(
        request.params.name,
        request.params.arguments || {},
        taskManager
      );
      // SDK automatically handles:
      // - Wrapping the returned value (success data or isError:true object) in `result: { ... }`
      // - Catching re-thrown protocol errors and formatting the top-level `error: { ... }`
    });
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 states it reads 'all information' including 'tasks' statuses, which hints at a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, returns paginated data, or what happens if the project ID is invalid. For a tool with no 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 that front-loads the core action ('read all information') and includes key details (resource, identifier, included data). There is no wasted language, and it effectively communicates the purpose without redundancy.

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 low complexity (one parameter, no output schema, no annotations), the description is adequate but not complete. It covers the basic purpose and parameter usage, but lacks details on behavioral aspects like error handling or return format. With no output schema, it should ideally hint at what 'all information' includes, but it does mention tasks' statuses, which adds some context.

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?

The schema description coverage is 100%, with the parameter 'projectId' well-documented in the schema. The description adds minimal value beyond the schema by mentioning 'by its ID', but doesn't provide additional context like format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('read') and resource ('project'), specifying it retrieves 'all information' including 'tasks' statuses. It distinguishes from siblings like 'list_projects' (which lists multiple) and 'read_task' (which reads a single task), though not explicitly. However, it doesn't fully differentiate from potential overlaps like 'get_next_task' or 'generate_project_plan' in terms of scope.

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 by stating 'by its ID', suggesting it's for reading a specific project rather than listing all. However, it doesn't explicitly state when to use this versus alternatives like 'list_projects' for overviews or 'read_task' for task details, nor does it mention prerequisites or exclusions. The guidance is present but not comprehensive.

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/chriscarrollsmith/taskqueue-mcp'

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