Skip to main content
Glama
FOX2920

WeWork MCP Server

by FOX2920

get_project_details

Retrieve detailed project information from WeWork project management data by providing a project ID to access basic project details.

Instructions

Lấy chi tiết của một dự án

Args:
    project_id: ID của dự án

Returns:
    Chi tiết dự án bao gồm thông tin cơ bản

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • The main handler function for the 'get_project_details' MCP tool. It is decorated with @mcp.tool() which serves as both registration and schema generation via function signature and docstring. Fetches project details using the WeWorkClient.
    @mcp.tool()
    def get_project_details(project_id: str) -> Dict[str, Any]:
        """
        Lấy chi tiết của một dự án
        
        Args:
            project_id: ID của dự án
        
        Returns:
            Chi tiết dự án bao gồm thông tin cơ bản
        """
        try:
            if not wework_client:
                return {'error': 'WeWork client not initialized'}
            
            logger.info(f"Getting project details for ID: {project_id}")
            project_info = wework_client.get_project_info(project_id)
            
            if project_info:
                return {
                    'success': True,
                    'project': project_info
                }
            else:
                return {
                    'error': f'Không tìm thấy dự án với ID: {project_id}',
                    'success': False
                }
        except Exception as e:
            logger.error(f"Error in get_project_details: {e}")
            return {'error': str(e), 'success': False}
  • Supporting helper method in WeWorkClient class that retrieves basic project information by matching project_id against fetched projects list.
    def get_project_info(self, project_id: str) -> Optional[Dict]:
        """Lấy thông tin cơ bản của project"""
        projects = self.fetch_projects()
        for project in projects:
            if project['id'] == project_id:
                return project
        return None
  • The @mcp.tool() decorator registers the get_project_details function as an MCP tool.
    @mcp.tool()
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 retrieves project details including basic information, which implies a read-only operation, but doesn't specify whether authentication is required, rate limits exist, what happens if the project_id doesn't exist, or the format of returned data. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise and well-structured with clear sections for Args and Returns. Each sentence earns its place: the purpose statement, parameter explanation, and return value description. No wasted words or redundant information.

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 simple nature (single parameter, no output schema, no annotations), the description is minimally adequate. It explains what the tool does and documents the parameter, but doesn't provide enough context about behavioral aspects like error conditions, authentication requirements, or data format. For a basic read operation, this is the minimum viable description.

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 description explicitly documents the single parameter 'project_id' with its purpose ('ID của dự án' - ID of the project), adding meaningful context beyond the schema which has 0% description coverage. Since there's only one parameter and the description fully explains it, this compensates well for the schema's lack of descriptions.

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 as 'Lấy chi tiết của một dự án' (Get details of a project), which is a specific verb+resource combination. It distinguishes from siblings like 'analyze_project_tasks' or 'get_project_statistics' by focusing on basic project details rather than analysis or statistics. However, it doesn't explicitly differentiate from 'find_project_by_name' which might also retrieve project details.

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 doesn't mention when to choose this over 'find_project_by_name' (which might search by name instead of ID) or 'search_projects' (which might return multiple projects). There are no explicit when/when-not instructions or prerequisites for usage.

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/FOX2920/Aplus-MCP'

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