Skip to main content
Glama

ui_select_project

Switch the active project in the UI by providing a project ID, so subsequent actions apply to the selected project.

Instructions

App-only: switch active project in the UI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "ui_select_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the switch persists across sessions, whether it affects other tools' default scope, what happens on an invalid or unknown project_id, nor what the call returns. For a state-mutating UI tool this is a substantial gap.

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?

One compact sentence with the constraint ('App-only') front-loaded and zero filler. It is appropriately sized for a one-parameter tool, though the brevity is partly under-specification rather than pure economy.

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

Completeness2/5

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

Given no annotations, no output schema, and 0% parameter coverage, the definition leaves an agent unable to determine prerequisites, side effects, or failure behavior before invoking a state-changing operation. It is not adequate for a mutation tool even a simple one.

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

Parameters2/5

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

Schema description coverage is 0% and the description says nothing about project_id — not its expected format, nor where to obtain a valid value (e.g., from project_list). The single parameter is left entirely unqualified by both structured and natural-language documentation.

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?

States a concrete verb ('switch') and resource ('active project'), plus the surface ('in the UI'), so the agent knows this mutates active-project state rather than creating or reading a project. It does not differentiate from siblings like ui_create_project or project_get, leaving that inference to names alone.

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 'App-only' prefix functions as a partial when-not constraint (not for headless/API contexts), but there is no explicit routing guidance such as 'use project_list to discover IDs first' or 'use project_get to read details without switching'. Usage is only implied.

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