Skip to main content
Glama

get_project_status

Check trace project status to view configuration, cache state, and validation results for static analysis of schema mismatches.

Instructions

Get the status of a trace project including config, cache state, and last validation result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectDirYesRoot directory with .trace-mcp config

Implementation Reference

  • Zod input validation schema for the get_project_status tool.
    const GetProjectStatusInput = z.object({
      projectDir: z.string().describe('Root directory with .trace-mcp config'),
    });
  • src/index.ts:264-274 (registration)
    Registration of the get_project_status tool in the ListToolsRequestSchema handler response.
    {
      name: 'get_project_status',
      description: 'Get the status of a trace project including config, cache state, and last validation result.',
      inputSchema: {
        type: 'object',
        properties: {
          projectDir: { type: 'string', description: 'Root directory with .trace-mcp config' },
        },
        required: ['projectDir'],
      },
    },
  • Main execution handler for get_project_status within the CallToolRequestSchema switch statement. Loads project status using imported watch functions and returns formatted JSON response.
    case 'get_project_status': {
      const input = GetProjectStatusInput.parse(args);
      log(`Getting project status for: ${input.projectDir}`);
      
      const project = loadProject(input.projectDir);
      
      if (!project.exists()) {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              success: false,
              exists: false,
              error: `No trace project found at ${input.projectDir}`,
            }, null, 2),
          }],
        };
      }
      
      const config = project.config;
      const activeWatchers = listActiveWatchers();
      const isWatching = activeWatchers.includes(project.rootDir);
      
      let watcherStatus = null;
      if (isWatching) {
        const watcher = getWatcher(project);
        watcherStatus = watcher.getStatus();
      }
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            success: true,
            exists: true,
            projectDir: project.rootDir,
            traceDir: project.traceDir,
            config,
            isWatching,
            watcherStatus,
            paths: {
              producer: project.producerPath,
              consumer: project.consumerPath,
            },
          }, null, 2),
        }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but does not cover aspects like error handling (e.g., what happens if the project directory is invalid), performance considerations, or output format. The description lacks details on what 'status' entails beyond a high-level list.

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 purpose ('Get the status') and specifies key components (config, cache state, validation result). There is no wasted verbiage, and every word contributes to understanding the tool's function.

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 moderate complexity (single parameter, read-only operation) and lack of annotations or output schema, the description is minimally adequate. It covers what the tool does but lacks details on behavioral traits, error cases, or output structure, leaving gaps for an agent to infer usage correctly.

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 input schema has 100% description coverage, with 'projectDir' clearly documented as the root directory containing the .trace-mcp config. The description does not add any parameter-specific details beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema 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 'Get' and the resource 'status of a trace project', specifying what information is retrieved (config, cache state, and last validation result). It distinguishes itself from siblings like 'init_project' or 'trace_file' by focusing on status retrieval rather than creation or tracing operations.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as requiring an initialized project, or compare it to siblings like 'trace_usage' or 'watch' that might overlap in functionality. Usage is implied but not explicitly stated.

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/Mnehmos/trace-mcp'

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