Skip to main content
Glama

project_open

Open a project by name or create it if missing, then list its assets, analyses, timelines and renders; omit the name to list all projects.

Instructions

Open a project by name (creates it if missing) and list its assets, analyses, timelines and renders. With no name, lists projects.

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": "project_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
createNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a real side effect — the project is created if missing — which an agent must know before calling. But it omits that this creation is conditional on the `create` flag, does not say what happens on failure (e.g., name length limits, invalid names), and says nothing about whether the call is a read or a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the primary behavior stated first and the fallback mode second. Every clause carries information an agent needs.

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?

There is no output schema and no annotations, so the description must cover both behavior and returns. It enumerates what gets listed (assets, analyses, timelines, renders), which is helpful, but it leaves the `create` parameter and error conditions undocumented, which is a meaningful gap for a tool that can create state.

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%, so the description must explain both parameters, and it only half does. It explains `name` semantics including the empty case, but never mentions `create`, whose default of true is exactly what governs the destructive-ish creation behavior the description describes as unconditional.

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 and resource ("Open a project") and spells out both operating modes: named project with its assets/analyses/timelines/renders, or a project list when no name is given. That is far more informative than a tautology, though it never contrasts itself with plausible siblings such as catalog_list or open_in_player.

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?

It does give the condition that selects the alternate mode ("With no name, lists projects"), which is genuine when-to-use guidance for one branch. However, it offers no guidance on when to use this versus other discovery/opening tools, and no prerequisites or exclusions are stated.

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