Skip to main content
Glama

MCP Foundry — Build, Test & Publish MCP Servers

Open MCP Foundry Studio

open_foundry_app
Read-only

Open interactive Foundry directory and authenticated Builder workspace in a compatible MCP Apps host.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_foundry_app"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds meaningful context: the workspace is "authenticated" and the surface is "interactive," implying an auth-dependent UI launch. It stops short of saying what is returned (e.g., a resource/UI handle) or what happens in a non-compatible host.

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?

A single front-loaded sentence with the verb first and the qualifying host condition last; no filler or redundancy. It is slightly dense in that two distinct surfaces (directory and Builder workspace) are compressed into one clause without explaining their relationship.

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?

For a zero-parameter tool with annotations and no output schema, most of the burden is met by stating what opens and the host requirement. The gap is the ambiguity of "authenticated" — whether the tool performs authentication or requires an already-authenticated session — which an agent needs to know before calling it.

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 tool takes zero parameters, so there is no parameter meaning for the description to carry and the baseline is 4. The schema is empty and fully consistent with the description's lack of arguments.

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

Purpose4/5

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

The description names a specific verb ("Open") and two concrete resources ("interactive Foundry directory" and "authenticated Builder workspace"), so the agent knows this launches a UI surface rather than fetching data. It does not explicitly distinguish itself from siblings such as get_server_tools or search_servers, so differentiation is left to inference.

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

Usage Guidelines3/5

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

The phrase "in a compatible MCP Apps host" supplies an environment precondition that implies when this tool is usable, which is useful guidance. However, there is no explicit statement of when to prefer it over alternatives, no exclusion for incompatible clients, and no described fallback behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.