Skip to main content
Glama

list_apps

Read-only

Retrieve your organization's uploaded apps with app IDs, names, platforms, and bundle/package identifiers, optionally filtered by platform, to pick an app ID for starting sessions or listing builds.

Instructions

List your organization's uploaded apps: app id, name, platform and bundle id / package name. Sample apps (is_sample) are VibeView's examples, never this project's app. Pass an app id to dev_start (app) or list_builds.

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

Input Schema

NameRequiredDescriptionDefault
platformNoOnly apps for this platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already declares this a safe read, and the description adds value beyond that by naming the returned fields and clarifying the semantic meaning of is_sample entries. It does not cover pagination, ordering, or result size limits, which is the main remaining behavioral gap.

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?

Three short sentences, front-loaded with the resource and its fields, followed by the sample-app caveat and the follow-on tool hint. No redundant restatement of the tool name and every clause carries information.

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 one-parameter read tool with no output schema, the description correctly compensates by listing the returned fields and explaining the is_sample flag. Minor incompleteness remains around ordering, pagination, and whether every uploaded app (built or not) is returned.

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

Parameters3/5

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

The single platform parameter has full schema coverage including an enumerated set of values, so the schema carries the meaning. The description never mentions the platform filter, so it adds nothing beyond what structured data already provides; baseline 3 applies.

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 your organization's uploaded apps') and immediately enumerates what each entry contains (app id, name, platform, bundle id / package name). It also distinguishes real project apps from VibeView sample apps, so the agent knows the scope of the result set without opening the schema.

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 clear downstream usage: pass an app id to dev_start (app) or list_builds, which tells the agent what this tool feeds into. It also warns that is_sample entries are never this project's app, an explicit exclusion. It lacks an explicit statement of when NOT to use this tool, but no sibling lists apps, so the gap is minor.

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