Skip to main content
Glama

List Hosted Apps

list_apps
Read-onlyIdempotent

List this Project's Hosted Apps with current version, role_ids, role_names, effective audience (effective_audience), owner_user_id as publisher attribution and absolute opening URL. All Administrators have access, plus holders of the listed Roles.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 meaningful context beyond that: the access model ("All Administrators have access, plus holders of the listed Roles") and the fact that owner_user_id is rendered as publisher attribution.

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 sentences, front-loaded with the verb and resource, then the returned fields and the access rule. The parenthetical "(effective_audience)" pins a field name without wasted prose.

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?

With no output schema, the description carries the burden of describing the returned fields and it does so explicitly, including the access-control caveat. It stops short of stating ordering, pagination, or empty-result behavior, but for a zero-parameter list tool it is largely complete.

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 no parameters, so the baseline is 4; nothing about invocation is ambiguous. The description's field enumeration informs the caller about output shape rather than parameter meaning, which is a bonus rather than a substitute.

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 specific verb and resource ("List this Project's Hosted Apps") and enumerates what each entry carries (current version, role ids/names, effective audience, publisher attribution, opening URL). It is clearly distinguishable from a generic listing, though it doesn't explicitly separate itself from siblings like list_app_versions.

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 "this Project's" implies scope, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to an alternative tool such as list_app_versions for version-level data. Usage is inferable but left to the agent.

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