Skip to main content
Glama

List applications

list_applications
Read-only

List the organisation's Applications (source-repo-backed deliverables with CI/CD pipelines): name, repository, branch, state, and pipeline summary. Optional search filter and pagination. Read-only.

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_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
searchNoSubstring filter on the application name.
page_sizeNoPage size (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already carry readOnlyHint=true, so the trailing 'Read-only.' adds nothing beyond structured data. The genuinely useful disclosure is the enumeration of returned fields (name, repository, branch, state, pipeline summary), which compensates for the absent output schema, but nothing is said about ordering, result limits, or empty-result behavior.

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?

Three compact sentences with the scope and returned-field inventory front-loaded, then pagination, then the safety note. Almost no waste, though the closing 'Read-only.' is redundant with the annotation.

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-required-parameter list tool with no output schema, the description supplies exactly the missing piece, a field-level summary of what a record contains. Only minor gaps remain, such as default sort order and pagination termination.

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 schema already documents page, page_size (default 20, max 100), and the substring nature of search. The description only restates 'search filter and pagination' at a higher level, so it adds no meaning the schema lacks; 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?

A specific verb (List) and a precisely scoped resource (the organisation's Applications), with a parenthetical defining what an Application is (source-repo-backed deliverables with CI/CD pipelines) and an enumeration of the fields returned. This distinguishes it from get_application, but it never explicitly names the sibling for single-record lookups.

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 mention of an 'Optional search filter and pagination' implies how to narrow or page results, but there is no explicit when-to-use guidance, no statement of when to prefer get_application, and no exclusions. Usage is inferable rather than stated.

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.