Skip to main content
Glama
qwert666

Foundry MCP Server

by qwert666
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

execute_function

Run Foundry functions with specified parameters to process data and perform operations within the platform.

Instructions

Execute a function using given parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_api_nameYes
parametersYes

Implementation Reference

  • src/mcp_server_foundry/server.py:130-143 (handler)
    The core handler implementation for the 'execute_function' tool, which executes a Foundry ontology query using the provided API name and parameters.
    @mcp.tool()
def execute_function(query_api_name: str, parameters: dict, ctx: Context):
    """ Execute a function using given parameters """

    foundry_client: FoundryClient = ctx.request_context.lifespan_context.foundry_client
    ontology_id: str = ctx.request_context.lifespan_context.ontology_id

    results = foundry_client.ontologies.Query.execute(
        ontology_id,
        query_api_name,
        parameters=parameters
    )
    return results

Tool Definition Quality

D1.6/5.0
Behavior1/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 but offers none. It doesn't indicate whether this is a read or write operation, what permissions are required, whether it's idempotent, what happens on failure, or any rate limits. 'Execute a function' could imply anything from a simple calculation to a destructive database operation with no safety information.

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 extremely concise - a single sentence with no wasted words. While this brevity contributes to efficiency, it comes at the cost of meaningful content. The structure is simple and front-loaded, but the content is insufficient for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's apparent complexity (executing functions with parameters), lack of annotations, 0% schema coverage, no output schema, and presence of sibling tools, the description is completely inadequate. It provides no context about what system this operates in, what functions are available, what the execution entails, or how results are returned.

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

Parameters1/5

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

With 0% schema description coverage and 2 parameters (including a nested object), the description provides no meaningful parameter semantics. It mentions 'given parameters' but doesn't explain what 'query_api_name' represents, what format 'parameters' should take, or provide any examples. The description fails to compensate for the complete lack of schema documentation.

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

Purpose2/5

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

The description 'Execute a function using given parameters' is a tautology that essentially restates the tool name 'execute_function'. It doesn't specify what kind of functions, what system they're executed in, or what the execution entails. While it mentions 'using given parameters', this adds minimal clarification beyond the name itself.

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

Usage Guidelines1/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 the sibling tools (list_functions, list_ontology_types, query_dataset, query_ontology_type). There's no mention of prerequisites, appropriate contexts, or distinctions from alternatives. The agent receives no help in selecting this tool over others.

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/qwert666/mcp-server-foundry'

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