Skip to main content
Glama
kumo-ai

KumoRFM MCP Server

Official
by kumo-ai

📖 Reading…

get_docs
Read-only

Retrieve documentation on using KumoRFM for predictive analytics on relational data, including graph setup, predictive queries, and explainability.

Instructions

Get documentation on how to use KumoRFM.

KumoRFM is a pre-trained Relational Foundation Model (RFM) that generates training-free predictions on any relational multi-table data by interpreting the data as a (temporal) heterogeneous graph. It can be queried via the Predictive Query Language (PQL).

Internal note: It is NOT related to "Recency, Frequency, Monetary" analysis.

Internally, KumoRFM utilizes in-context learning to transfer patterns from historical examples to new unseen examples. Specifically, it constructs training/in-context subgraphs with known ground-truth labels and relates them to unseen subgraphs.

See the 'kumo://docs/overview' resource for more information.

KumoRFM can discover table-like files (e.g., CSV, Parquet), inspect them, and structure them into a graph via foreign key-primary key relationships. A time column in a table dictates the create time of a row, which is used downstream to receive and order historical interactions and prevent temporal leakage. Each column within a table is assigned a semantic type (numerical, categorical, multi-categorical, ID, text, timestamp, sequence, etc) that denotes the semantic meaning of the column and how it should be processed within the model.

Important: Before creating and updating graphs, read the documentation first at 'kumo://docs/graph-setup'.

After a graph is set up and materialized, KumoRFM can generate predictions (e.g., missing value imputation, temporal forecasts) and evaluations by querying the graph via the Predictive Query Language (PQL), a declarative language to formulate machine learning tasks. Understanding PQL and how it maps to a machine learning task is critical to achieve good model predictions. Besides PQL, various other options exist to tune model output, e.g., optimizing the run_mode of the model, specifying how subgraphs are formed via num_neighbors, or adjusting the anchor_time to denote the point in time for when a prediction should be made.

Important: Before executing or suggesting any predictive queries, read the documentation first at 'kumo://docs/predictive-query'.

KumoRFM can additionally generate explanations for predictions, providing both a global column-level analysis and a local, cell-level attribution view. Together, these views enable comprehensive interpretation.

Important: Before analyzing the explanation output, read the documentation first at 'kumo://docs/explainability'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource_uriYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description fully aligns with the annotations (readOnlyHint=true, destructiveHint=false). It adds context such as the tool being purely informational, the importance of reading specific docs before certain actions, and internal notes. No contradictions.

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 thorough but somewhat lengthy. It is well-structured with sections and highlighted important points, which is appropriate for a documentation tool. However, it could be slightly more concise without losing clarity.

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?

The description covers all necessary aspects: what the tool does, when to use it, parameter details, and additional context like the internal note and prerequisite readings. With an output schema present (indicated by context signals), the lack of return value description is acceptable.

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 explicitly lists the four possible resource URIs from the enum and explains what each documentation resource covers (e.g., 'kumo://docs/overview' for overview, 'kumo://docs/graph-setup' for graph setup). With schema description coverage at 0%, the description compensates fully by adding meaning to the parameter.

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

Purpose5/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: 'Get documentation on how to use KumoRFM.' It uses a specific verb ('Get') and resource ('documentation'), and distinguishes itself from sibling tools, none of which are documentation-focused.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool, including 'Important: Before creating and updating graphs, read the documentation first at ...', 'Before executing or suggesting any predictive queries, read ...', and 'Before analyzing the explanation output, read ...'. It also includes an internal note to avoid confusion with other meanings of RFM.

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/kumo-ai/kumo-rfm-mcp'

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