Skip to main content
Glama

get_project

Retrieve cryptocurrency project details by ID, with options to include team members and investors for comprehensive analysis.

Instructions

Obtain project details according to the project ID.

Args:
    project_id: The unique identifier for the project.
    include_team: Whether to include team member information, default is false.
    include_investors: Whether to include investor information, default is false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
include_teamNo
include_investorsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The async handler function that implements the core logic of the 'get_project' MCP tool, handling API calls and response formatting.
    async def get_project(
        project_id: int,
        include_team: bool = False,
        include_investors: bool = False,
    ) -> str:
        """Obtain project details according to the project ID.
    
        Args:
            project_id: The unique identifier for the project.
            include_team: Whether to include team member information, default is false.
            include_investors: Whether to include investor information, default is false.
        """
        # Prepare request data
        data = {
            "project_id": project_id,
            "include_team": include_team,
            "include_investors": include_investors,
        }
        
        # Fetch data from the API
        response = await make_request("get_item", data)
        
        # Check if there was an error
        if "Error" in response:
            return f"Error: {response['Error']}"
        
        # Check if data is found
        if response.get("result") != 200 or not response.get("data"):
            return f"No project found with ID {project_id}."
        
        # Return the formatted results
        return json.dumps(response["data"], indent=2)
  • server.py:76-76 (registration)
    The decorator that registers 'get_project' as an MCP tool with FastMCP.
    @mcp.tool()
  • Input schema defined by function parameters with type hints and comprehensive docstring describing args.
    async def get_project(
        project_id: int,
        include_team: bool = False,
        include_investors: bool = False,
    ) -> str:
        """Obtain project details according to the project ID.
    
        Args:
            project_id: The unique identifier for the project.
            include_team: Whether to include team member information, default is false.
            include_investors: Whether to include investor information, default is false.
        """
  • Supporting helper function used by get_project to perform the actual HTTP request to RootData API.
    async def make_request(endpoint: str, data: dict) -> dict[str, any] | None:
        """Make a request to the RootData API with proper error handling."""
        headers = {
            "Content-Type": "application/json",
            "language": "en",
        }
        
        if api_key := os.environ.get("ROOTDATA_API_KEY"):
            headers["apikey"] = api_key
        else:
            return {"Error": "ROOTDATA_API_KEY environment variable is not set"}
    
        url = f"{ROOTDATA_API_BASE}/{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                response = await client.post(url, headers=headers, json=data, timeout=30.0)
                response.raise_for_status()
                return response.json()
            except Exception as e:
                return {"Error": str(e)}
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. While it describes the basic operation, it doesn't mention whether this is a read-only operation, if it requires authentication, what happens with invalid project IDs, or any rate limits. The description is functional but lacks important behavioral context.

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 and appropriately sized. The purpose is stated clearly in the first sentence, followed by a parameter section. While efficient, the parameter explanations could be slightly more concise, and the overall description could benefit from more usage context.

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 that there's an output schema (which handles return values), the description provides good coverage of the tool's purpose and parameters. However, for a tool with no annotations and sibling tools available, it should include more guidance on when to use this versus alternatives and mention any behavioral constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter semantics that go beyond the input schema. While the schema has 0% description coverage, the description clearly explains what each parameter does ('unique identifier for the project', 'whether to include team member information', 'whether to include investor information') and provides default values. This fully compensates 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 with a specific verb ('Obtain') and resource ('project details'), making it easy to understand what the tool does. However, it doesn't differentiate this tool from its sibling 'get_organization' or explain how it differs from 'search' for project-related queries.

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 like 'get_organization' or 'search'. It mentions default values for optional parameters but doesn't explain scenarios where including team or investor information would be beneficial.

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/jincai/rootdata-mcp-server'

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