Foundry MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN | No | A user token that you can generate in your profile page | |
| SCOPES | No | Oauth scopes | None |
| HOSTNAME | No | Your hostname of your Foundry instance | |
| CLIENT_ID | No | A service user that is created in developer console | |
| ONTOLOGY_ID | No | Your ontology id | |
| CLIENT_SECRET | No | A secret associated with the service user |
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
| Name | Description |
|---|---|
| list_ontology_typesC | List all the ontology types |
| query_ontology_typeA | Query for objects in a given ontology type. Use list_ontology_types to get the list of available types |
| query_datasetC | Query a dataset using Spark SQL dialect e.g. "SELECT COUNT(*) FROM |
| list_functionsB | List all available functions |
| execute_functionD | Execute a function using given parameters |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap. execute_function runs code, list_functions enumerates functions, list_ontology_types lists types, query_dataset queries datasets, and query_ontology_type queries specific ontology types. The descriptions clearly differentiate their scopes and usage contexts.
All tools follow a consistent verb_noun pattern using snake_case. The verbs (execute, list, query) are appropriately chosen for their actions, and the nouns (function, ontology_type, dataset) clearly indicate the target resources. No deviations or mixed conventions are present.
With 5 tools, this server is well-scoped for its apparent domain of data and function management in a Foundry context. Each tool serves a distinct and necessary purpose, covering listing, querying, and execution operations without bloat or redundancy.
The toolset provides solid coverage for querying and listing operations on functions, datasets, and ontology types, with execute_function enabling action. A minor gap exists in update/delete operations for these resources, but agents can likely work with the provided read/execute capabilities for common workflows.