Skip to main content
Glama

get_project_detail

Retrieve detailed statistics and activity data for a specific coding project from Wakapi time tracking. Fetch project information including creation date, last activity, and development metrics.

Instructions

Retrieve a single project.

Mimics undocumented endpoint related to https://wakatime.com/developers#projects.

Requires ApiKeyAuth: Set header Authorization to your API Key encoded as Base64 and prefixed with Basic.

Args: id (str, required): Project ID to fetch. user (str, required, default="current"): User ID to fetch data for (or 'current').

Returns: v1.ProjectViewModel: - data (Project): - id (str): Project ID. - name (str): Project name. - urlencoded_name (str): URL encoded name. - created_at (str): Creation timestamp. - last_heartbeat_at (str): Last activity timestamp. - human_readable_last_heartbeat_at (str): Human readable last activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
userNocurrent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_project_detail' tool, decorated with @app.tool. It retrieves project details using the Wakapi client and includes input/output schema in the docstring.
    @app.tool
    async def get_project_detail(id: str, user: str = "current") -> dict[str, Any]:
        """Retrieve a single project.
    
        Mimics undocumented endpoint related to https://wakatime.com/developers#projects.
    
        Requires ApiKeyAuth: Set header `Authorization` to your API Key encoded as Base64
        and prefixed with `Basic`.
    
        Args:
            id (str, required): Project ID to fetch.
            user (str, required, default="current"): User ID to fetch data for
            (or 'current').
    
        Returns:
            v1.ProjectViewModel:
            - data (Project):
              - id (str): Project ID.
              - name (str): Project name.
              - urlencoded_name (str): URL encoded name.
              - created_at (str): Creation timestamp.
              - last_heartbeat_at (str): Last activity timestamp.
              - human_readable_last_heartbeat_at (str): Human readable last activity.
        """
        client = get_wakapi_client()
    
        try:
            project = await client.get_project_detail(user=user, id=id)
            return project.model_dump()
        except Exception as e:
            raise ValueError(f"Failed to fetch project detail: {e}") from e
  • main.py:145-147 (registration)
    Registration of the 'get_project_detail' tool by importing and referencing it in the initialize_tools function.
    from mcp_tools.project_detail import get_project_detail
    
    _ = get_project_detail  # Trigger registration
Behavior4/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 effectively describes key traits: it's a read operation ('Retrieve'), requires authentication (ApiKeyAuth with specific header format), and mimics an undocumented endpoint. It doesn't cover rate limits, error handling, or pagination, but for a simple retrieval tool, this is reasonably transparent.

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?

The description is well-structured with clear sections (purpose, endpoint reference, authentication, args, returns) and uses bullet points for returns. It's appropriately sized for the tool's complexity, but the authentication details could be slightly more concise, and some sentences are a bit lengthy.

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

Completeness5/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 (2 parameters, no annotations, but with an output schema), the description is complete enough. It covers purpose, authentication, parameters, and return values in detail. The output schema is provided, so the description doesn't need to explain return values extensively, and it adds useful context like the endpoint mimicry.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaningful semantics for both parameters: 'id' is explained as 'Project ID to fetch', and 'user' is detailed as 'User ID to fetch data for (or 'current')', including the default value. This goes beyond the schema's basic titles, though it could provide more context on valid formats or constraints.

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 ('Retrieve') and resource ('a single project'), making the purpose unambiguous. It distinguishes this from sibling tools like 'get_projects' (plural) by specifying it fetches a single project. However, it doesn't explicitly contrast with other siblings like 'get_user' or 'get_stats', so it's not a perfect 5.

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 mentioning it 'mimics undocumented endpoint related to https://wakatime.com/developers#projects', which provides context. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_projects' or other siblings, and doesn't specify prerequisites or exclusions beyond the authentication note.

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/impure0xntk/mcp-wakapi'

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