Skip to main content
Glama

List applications

gameye_list_applications
Read-onlyIdempotent

List your organization's Gameye applications, including registry, repository, resources, regions, and ports, to inspect which images Gameye can run.

Instructions

List your organization's applications (images Gameye can run) with registry, repository, resources, regions and ports. Needs the application:read scope. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, yet the description adds non-obvious behavior: the application:read scope requirement and the fallback that with no GAMEYE_API_TOKEN it returns setup steps and sends nothing. That no-op fallback is valuable operational context not captured anywhere in the structured fields; only return format details are absent.

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 compact sentences: purpose and payload first, then the permission prerequisite, then the token fallback. Nothing is repeated from the schema or annotations and no sentence is filler.

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 zero-parameter read tool with no output schema, the description supplies the necessary auth prerequisites, the degraded-mode behavior, and an outline of returned fields. It is essentially complete; only minor details such as result ordering or pagination are unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema. The listed output fields (registry, repository, resources, regions, ports) give some sense of the result shape but are not parameter semantics; a neutral baseline applies for a no-arg tool.

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 your organization's applications') and even clarifies the domain term ('images Gameye can run'). It also previews returned fields, making it clearly distinguishable from write siblings like gameye_create_application or gameye_edit_application, though it never names an alternative explicitly.

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 implied by the word 'List' and the read-scope requirement, but there is no explicit when-to-use guidance or mention of when another sibling (e.g. gameye_list_registry_tags, gameye_list_regions) would be the better choice. The prerequisite scope is the only real routing signal.

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