Skip to main content
Glama
mdz-axo

PT-MCP (Paul Test Man Context Protocol)

by mdz-axo

watch_project

Monitor project directories for file changes and automatically update context formats to maintain current codebase understanding.

Instructions

Start monitoring project for changes and auto-update context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRoot directory path to watch
context_formatsYesContext formats to auto-update
debounce_msNoDebounce delay in milliseconds
watch_patternsNoGlob patterns to watch

Implementation Reference

  • The core handler function for the 'watch_project' tool, which currently returns a placeholder response indicating implementation is pending.
    export async function watchProject(
      args: WatchProjectArgs
    ): Promise<{ content: Array<{ type: string; text: string }> }> {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                message: "Project watching - implementation pending",
                path: args.path,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Type definition (schema) for the input arguments of the watchProject handler.
    interface WatchProjectArgs {
      path: string;
      context_formats: string[];
      debounce_ms?: number;
      watch_patterns?: string[];
    }
  • Registration of the watch_project tool handler in the switch statement for tool requests.
    case "watch_project":
      return await watchProject(args as any);
  • Full MCP tool schema registration including inputSchema, description, and required fields in the ListTools response.
    {
      name: "watch_project",
      description: "Start monitoring project for changes and auto-update context",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description: "Root directory path to watch",
          },
          context_formats: {
            type: "array",
            items: { type: "string" },
            description: "Context formats to auto-update",
          },
          debounce_ms: {
            type: "number",
            description: "Debounce delay in milliseconds",
            default: 1000,
          },
          watch_patterns: {
            type: "array",
            items: { type: "string" },
            description: "Glob patterns to watch",
          },
        },
        required: ["path", "context_formats"],
      },
    },
  • Import statement registering the watchProject handler for use in tool dispatch.
    import { watchProject } from "./watch-project.js";
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions 'auto-update context' but doesn't specify what triggers updates, how long monitoring persists, resource implications, or error handling. The description is insufficient for a tool with ongoing side effects.

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 functionality. Every word earns its place with no redundancy or fluff, making it highly concise and well-structured.

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 the tool's complexity (ongoing monitoring with side effects), no annotations, and no output schema, the description is incomplete. It lacks details on monitoring scope, update mechanisms, termination conditions, and error scenarios, leaving significant gaps for agent understanding.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage without extra value.

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 with specific verbs ('Start monitoring', 'auto-update') and identifies the resource ('project for changes', 'context'). It distinguishes from siblings like 'update_context' by emphasizing continuous monitoring rather than one-time updates, though it doesn't explicitly name alternatives.

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 for continuous monitoring scenarios but doesn't explicitly state when to use this versus alternatives like 'update_context' for manual updates or 'enrich_context' for enhancement. No guidance on prerequisites or exclusions is provided.

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/mdz-axo/pt-mcp'

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