Skip to main content
Glama

list_apps

Read-only

The apps this key reaches, each a service that sends errors, with its id and slug. With project, only that project's.

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
projectNoA project's id or slug, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "A project's id or slug, from list_projects.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuinely non-obvious behavioral fact beyond the annotations: the result set is bounded by what 'this key reaches', i.e. results depend on API key permissions, not just on the filter. It stops short of describing ordering or whether all apps or only error-sending ones are returned.

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?

Two short sentences with no filler, and the scope statement is front-loaded before the optional filter. The phrasing 'each a service that sends errors' is slightly awkward but earns its place by defining what an app is.

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

Completeness5/5

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

For a single-optional-parameter read tool with full schema coverage and annotations, the description covers what is listed, what the items look like (id, slug), how the key constrains results, and how the filter behaves. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100% and the project property already explains itself as 'A project's id or slug, from list_projects.' The description only restates that supplying it narrows results to that project, adding no format or edge-case detail. Baseline 3 is appropriate when the schema carries the semantics.

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 the resource ('The apps this key reaches') and adds a defining gloss — each app is 'a service that sends errors' — plus the returned identifiers (id and slug). That is specific enough to distinguish it from get_app and from unrelated list_* siblings, though it never explicitly names an alternative tool.

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?

Usage is only implied: 'With project, only that project's' tells the agent the parameter narrows results, but there is no explicit statement of when to call this versus get_app or how to enumerate everything. The agent must infer that omitting the parameter returns the full key-scoped set.

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