Skip to main content
Glama

info

Retrieve server details including database location, statistics, and usage information for the Technical Project Manager MCP server.

Instructions

Get information about the tracker MCP server: database location, stats, and usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'info' tool. Generates a comprehensive markdown report about the MCP server, including database location and size, current project stats, installation instructions, list of available tools, and migration info.
        # Info
        if name == "info":
            import os
    
            roadmap = db.get_roadmap()
            db_size = os.path.getsize(DEFAULT_DB_PATH) if DEFAULT_DB_PATH.exists() else 0
            db_size_mb = db_size / (1024 * 1024)
    
            info = f"""# Tracker MCP Server
    
    ## Database
    - **Location**: `{DEFAULT_DB_PATH}`
    - **Size**: {db_size_mb:.2f} MB
    - **Mode**: SQLite with WAL (concurrent read/write safe)
    
    ## Current Stats
    - **Organizations**: {len(roadmap.orgs)}
    - **Projects**: {sum(len(o.projects) for o in roadmap.orgs)}
    - **Tickets**: {roadmap.stats.get("total_tickets", 0)} ({roadmap.stats.get("tickets_done", 0)} done)
    - **Tasks**: {roadmap.stats.get("total_tasks", 0)} ({roadmap.stats.get("tasks_done", 0)} done)
    - **Completion**: {roadmap.stats.get("completion_pct", 0)}%
    
    ## Installation
    
    Add to Claude Code with:
    ```bash
    claude mcp add tracker --scope user -- uv run --directory /path/to/tpm-mcp tpm-mcp
    ```
    
    ## Available Tools
    - `roadmap_view` - Project overview (filterable by project, active_only)
    - `ticket_list` - List ticket IDs with status/priority (paginated)
    - `ticket_get` - Get ticket details (minimal/summary/full)
    - `ticket_create/update` - Create or update tickets
    - `task_list` - List task IDs with status (paginated)
    - `task_get` - Get full task details
    - `task_create/update` - Create or update tasks
    - `note_list` - List notes with preview (paginated)
    - `note_get` - Get full note content
    - `note_add` - Add a note to any entity
    - `org_list/create` - Manage organizations
    - `project_list/create` - Manage projects
    - `info` - This info page
    
    ## Migration
    To import from JSON project tracker:
    ```bash
    uv run python -m tpm_mcp.migrate /path/to/project-tracker
    ```
    """
            return info
  • Registration of the 'info' tool in the server.list_tools() handler, including its name, description, and empty input schema (no parameters required).
        Tool(
            name="info",
            description="Get information about the tracker MCP server: database location, stats, and usage.",
            inputSchema={"type": "object", "properties": {}},
        ),
    ]
  • Input schema for the 'info' tool: an empty object, indicating no input parameters are required.
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior3/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 the tool retrieves information, implying a read-only operation, but doesn't specify behavioral traits like authentication needs, rate limits, or potential side effects (e.g., if it logs usage). It adds value by detailing the types of information returned, but lacks depth on operational constraints.

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 ('Get information') and specifies the resource and details without waste. Every word earns its place by clarifying scope and content, making it easy to parse quickly.

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 (0 parameters, no output schema, no annotations), the description is reasonably complete for a simple info-fetching tool. It specifies what information is retrieved, but lacks details on output format, error handling, or server-specific nuances. Without annotations or output schema, more context on return values would be beneficial for full 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% description coverage, so the schema fully documents the lack of inputs. The description adds no parameter-specific information, which is appropriate here. Baseline is 4 for zero parameters, as no compensation is needed for schema gaps.

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 a specific verb ('Get') and resource ('information about the tracker MCP server'), including what information is retrieved (database location, stats, and usage). It distinguishes itself from sibling tools that focus on notes, orgs, projects, tasks, and tickets rather than server metadata. However, it doesn't explicitly differentiate from potential similar tools like 'status' or 'health' that might exist elsewhere.

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 by specifying what information is retrieved, suggesting it's for server diagnostics or monitoring. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., for checking server status vs. querying data), nor does it mention prerequisites or exclusions. The context is clear but lacks detailed when/when-not instructions.

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/urjitbhatia/tpm-mcp'

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