Skip to main content
Glama
paulieb89

PyP6Xer MCP Server

pyp6xer_slipping_activities

Read-onlyIdempotent

Find activities running late where forecast finish exceeds baseline finish. Filter by minimum slip days to pinpoint delays.

Instructions

Find activities that are running late (forecast finish > baseline finish).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cache_keyNoCache key identifying the loaded XER file (set when calling pyp6xer_load_file)default
proj_idNoProject ID or short name; uses first project if omitted
min_days_slipNoOnly return activities slipping by at least this many days

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:995-1001 (registration)
    Tool registration via @mcp.tool decorator on pyp6xer_slipping_activities function
    @mcp.tool(annotations=ToolAnnotations(readOnlyHint=True, destructiveHint=False, idempotentHint=True, openWorldHint=False))
    def pyp6xer_slipping_activities(
        cache_key: Annotated[str, Field(description="Cache key identifying the loaded XER file (set when calling pyp6xer_load_file)")] = "default",
        proj_id: Annotated[str | None, Field(description="Project ID or short name; uses first project if omitted")] = None,
        min_days_slip: Annotated[int, Field(description="Only return activities slipping by at least this many days", ge=0)] = 0,
        ctx: Context = None,
    ) -> str:
  • Actual handler implementation: finds activities running late (forecast finish > baseline finish), filters by min_days_slip, sorts descending by slip
    def pyp6xer_slipping_activities(
        cache_key: Annotated[str, Field(description="Cache key identifying the loaded XER file (set when calling pyp6xer_load_file)")] = "default",
        proj_id: Annotated[str | None, Field(description="Project ID or short name; uses first project if omitted")] = None,
        min_days_slip: Annotated[int, Field(description="Only return activities slipping by at least this many days", ge=0)] = 0,
        ctx: Context = None,
    ) -> str:
        """Find activities that are running late (forecast finish > baseline finish).
    
        Args:
            cache_key:     Cache key of the loaded file.
            proj_id:       Optional project filter.
            min_days_slip: Only return activities slipping by at least this many days (default 0).
        """
        xer = _get_xer(ctx, cache_key)
        tasks = _get_tasks(xer, proj_id)
    
        slipping = []
        for t in tasks:
            if t.status.is_completed:
                continue
            try:
                forecast = t.finish
            except Exception:
                continue
            baseline = t.target_end_date
            slip = (forecast - baseline).days
            if slip > min_days_slip:
                d = _task_to_dict(t)
                d["forecast_finish"] = _fmt_date(forecast)
                d["slip_days"] = slip
                slipping.append(d)
    
        slipping.sort(key=lambda x: -x["slip_days"])
        return json.dumps({
            "slipping_count": len(slipping),
            "min_days_slip_filter": min_days_slip,
            "activities": slipping,
        }, indent=2)
Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description reinforces a safe read-only operation. No contradictions; provides the specific comparison logic (forecast vs baseline) beyond annotations.

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?

Single concise sentence with parenthetical clarification. Efficient but could briefly mention optional filter (min_days_slip) to improve front-loading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given simple tool with 3 optional parameters, output schema, and clear annotations, description sufficiently explains purpose and behavior. Minor gaps in usage context but overall adequate.

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?

Input schema covers 100% of 3 parameters with descriptions. Description does not add extra semantic detail beyond what schema provides, so baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool finds slipping activities with explicit condition (forecast finish > baseline finish). Distinguishes from sibling tools like pyp6xer_list_activities (general list) and pyp6xer_float_analysis (float analysis).

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?

No explicit guidance on when to use this tool versus alternatives. Context signals and siblings exist but description does not direct the agent to use this for slipping analysis vs other schedule analysis tools.

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/paulieb89/pyp6xer-mcp'

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