Skip to main content
Glama

List apps

projects
Read-onlyIdempotent

List this signed-in user’s persistent Tofu projects: [] when the account has no app yet, and ingestFiles with a name creates its first app from this chat. A row carries sourceOrigin — { via: "browser" | "agent" | "github" | "builder", client? } — when Tofu recorded who uploaded that project’s current code, and omits it when the origin is unknown. This field records upload provenance, not verified identity. builder means the app was last changed in the Tofu builder: an upload from you replaces that version. A live app that has a private test copy also carries testCopy — the copy’s own { projectId, name, address } — and a copy is never a row of its own.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: an empty array for accounts with no apps, that `sourceOrigin` is omitted when provenance is unknown, that it records upload provenance rather than verified identity, and that `testCopy` is never a standalone row.

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 core purpose and empty-result behavior are front-loaded, and most of the remaining text (sourceOrigin values, builder semantics, testCopy) earns its place given there is no output schema. It is somewhat dense with em-dash chains and mixes a creation hint into the opening sentence, costing a little readability.

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

Completeness4/5

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

For a zero-parameter read tool with full annotation coverage and no output schema, the description carries the return-shape burden and does so for the non-obvious fields (`sourceOrigin`, `testCopy`, empty array). It leaves the obvious row fields (projectId, name, address) undescribed, which is a minor gap rather than a blocking one.

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 to add and the baseline applies. The description instead spends its space on row semantics, which is the right allocation for a no-arg tool.

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

Purpose5/5

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

States a specific verb and resource ('List this signed-in user's persistent Tofu projects') and immediately scopes it to the caller's own account. It also reconciles the title's 'apps' with 'projects' by naming ingestFiles as the creation path, so an agent can tell listing apart from creating.

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

Usage Guidelines4/5

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

Gives a clear usage signal in the empty-account case ('[] when the account has no app yet') and routes the agent to ingestFiles with a `name` when the user wants to create the first app. It stops short of explicit when-not-to-use or exclusion guidance, but there is no real competing listing sibling.

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.

Resources