Skip to main content
Glama

List the apps

list_apps
Read-only

Every Mayorana desktop app: id, name, what it does, platforms, latest version and page URL.

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
localeNoLanguage of the content: en or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and openWorldHint=false, so the safety profile is covered. The description's main added value is disclosing the returned fields (id, name, description, platforms, version, URL), which matters because there is no output schema. It says nothing about ordering, pagination, or whether unpublished apps are included.

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?

A single compact sentence that front-loads the scope ('Every Mayorana desktop app') and then enumerates the payload. No filler, though it is a sentence fragment rather than a full statement of action.

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?

For a zero-required-param, read-only list tool with one documented enum parameter, the description covers scope and return fields adequately. Gaps remain around result ordering, completeness of the enumeration (all apps vs. filtered), and how locale changes output, which an agent might need.

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%: the single 'locale' parameter is fully documented with an enum and default. The description never mentions locale or how it affects returned content, so it adds nothing beyond the schema — baseline 3 applies.

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 fragment 'Every Mayorana desktop app' with a field list makes clear this enumerates all desktop apps and returns id, name, description, platforms, version and URL. 'Every' implicitly contrasts with the single-app sibling get_app. It's clear but the verb (list/return) is only implied by the title, not the description.

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?

No statement of when to use this versus get_app, search, or get_release_notes, and no preconditions. The only hint is the word 'Every', which weakly implies a full-enumeration use case. An agent must infer that this is the bulk-list option.

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