Skip to main content
Glama

get_organization

Retrieve detailed information about cryptocurrency organizations from RootData by providing an organization ID. Optionally include team member and investment project data for comprehensive analysis.

Instructions

Obtain VC details according to VC ID.

Args:
    org_id: Organization ID
    include_team: Whether to include team member information, default is false.
    include_investments: Whether it includes investment project information, default is false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_idYes
include_teamNo
include_investmentsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler for the 'get_organization' tool. This async function is decorated with @mcp.tool(), defining the tool's input parameters, logic to call the RootData API endpoint 'get_org', error handling, and JSON-formatted response.
    @mcp.tool()
    async def get_organization(
        org_id: int,
        include_team: bool = False,
        include_investments: bool = False,
    ) -> str:
        """Obtain VC details according to VC ID.
    
        Args:
            org_id: Organization ID
            include_team: Whether to include team member information, default is false.
            include_investments: Whether it includes investment project information, default is false.
        """
        # Prepare request data
        data = {
            "org_id": org_id,
            "include_team": include_team,
            "include_investments": include_investments,
        }
        
        # Fetch data from the API
        response = await make_request("get_org", 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 organization found with ID {org_id}."
        
        # Return the formatted results
        return json.dumps(response["data"], indent=2)
  • Helper function used by get_organization (and other tools) to make HTTP requests to the RootData API, handling authentication, errors, and async HTTP calls.
    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?

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read-only operation ('Obtain'), but doesn't specify if it's safe, requires authentication, has rate limits, or what happens on errors. The description adds minimal context beyond the basic retrieval action, failing to compensate for the lack of 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?

The description is front-loaded with the purpose, followed by a structured 'Args' section that efficiently lists parameters with brief explanations. It avoids unnecessary fluff, though the phrasing 'Obtain VC details according to VC ID' is slightly redundant and could be more polished.

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 moderate complexity (3 parameters, 1 required), no annotations, but an output schema exists, the description is minimally adequate. It covers the purpose and parameters but lacks behavioral context and usage guidelines. The output schema reduces the need to explain return values, but overall completeness is limited by gaps in transparency and guidance.

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 schema description coverage is 0%, so the description carries the burden of explaining parameters. It clearly defines 'org_id' as 'Organization ID' and provides meaningful semantics for 'include_team' and 'include_investments' with default values, adding significant value beyond the bare schema. However, it doesn't detail data types or constraints, keeping it from a perfect score.

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

Purpose3/5

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

The description states the tool 'Obtain VC details according to VC ID,' which clarifies it retrieves information about venture capital organizations. However, it's somewhat vague about what 'VC details' specifically include beyond the optional team and investment parameters, and it doesn't differentiate from sibling tools like 'get_project' or 'search' in terms of scope or use case.

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 such as 'get_project' or 'search.' It lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent without clear direction on tool selection in relation to siblings.

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