Skip to main content
Glama

List apps

list_apps
Read-only

Tracked apps of the user, 20 per page by default. Use nextOffset for more.

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
limitNoResults per page (max 100)
offsetNoStart at this offset; use nextOffset from the previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 20,
      +  "description": "Results per page (max 100)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Start at this offset; use nextOffset from the previous response",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds a useful behavioral fact beyond that: results are paginated at 20 per page by default and continued via nextOffset. It does not describe what fields each app entry contains or whether an empty list signals no tracked apps.

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 the resource stated first and the pagination hint second; nothing is wasted. It is terse to the point of omitting scope details, but structure itself is sound.

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?

With a trivial two-parameter schema, no output schema, and readOnlyHint covering safety, the description is close to sufficient. It still leaves unclear whether the list is scoped to the authenticated user's account only and what a returned entry looks like.

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 description coverage is 100%, including limit (max 100) and offset semantics, so the baseline is 3. The description reinforces pagination but refers to "nextOffset" while the actual parameter is named "offset", which could momentarily confuse an agent even though the schema clarifies the link.

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 noun phrase "Tracked apps of the user" names the exact resource returned, which implicitly distinguishes it from siblings like add_app, search_app_store, and get_app_details. It lacks an explicit verb and never names an alternative, but the resource is unmistakable.

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

Usage Guidelines2/5

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

"Use nextOffset for more" is pagination mechanics, not when-to-use guidance. The description never says when to call this instead of get_app_details, add_app, or search_app_store, nor does it state any prerequisites.

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