Skip to main content
Glama
jincai

RootData MCP Server

by jincai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
searchB

Search for Project/VC/People brief information according to keywords.

Args:
    query: Search keywords, which can be project/institution names, tokens, or other related terms.
get_projectB

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.
get_organizationC

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_organization retrieves VC details, get_project retrieves project details, and search performs keyword-based searches across multiple entity types. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific objectives.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_organization, get_project, and search. The naming is uniform, using snake_case throughout, with clear and predictable verbs that accurately describe each tool's action.

Tool Count3/5

With only 3 tools, the server feels thin for a data-focused domain like VC and project details. While the tools cover basic retrieval and search, the scope suggests that additional operations (e.g., listing, filtering, or updating) might be expected, making the count borderline for comprehensive coverage.

Completeness3/5

The server provides read operations (get and search) but lacks create, update, or delete tools, which are typical for data management. This creates notable gaps in lifecycle coverage, as agents cannot modify or add data, limiting the server to query-only functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources