Skip to main content
Glama

list_applications

Read-only

Lists applications in your scope with their highest EU AI Act risk tier, optionally filtered by department, personal-data processing, or end-of-life date.

Instructions

List applications in the user's scope with their highest AI Act tier.

end_of_life_before is an ISO date, e.g. '2028-01-01' for apps retiring by end of 2027.

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
departmentNo
end_of_life_beforeNo
processes_personal_dataNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 by structured data. The description does add real behavioral value by disclosing that each returned application is annotated with its highest AI Act tier, and it clarifies the boundary semantics of the date filter. It says nothing about ordering, result limits, or what an empty result means, which is where the remaining gap lies.

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?

The primary purpose is front-loaded in the first sentence, with the parameter note demoted to a second block where it belongs. The ISO/example sentence is compact and contains no filler, though the definition could have folded the other two filters into a comparable note at little cost.

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?

An output schema exists and annotations cover safety, so return-format and mutation details are rightly omitted. What remains missing is the semantics of the two undocumented filters and whether they combine as AND or are independent, which matters for a three-parameter filtering tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does the hardest part well: it defines end_of_life_before as an ISO date and gives a worked example that reveals the boundary is explicit — '2028-01-01' returns apps retiring by end of 2027. Department and processes_personal_data remain entirely undocumented, so the coverage is improved but incomplete.

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 applications") plus a meaningful qualifier ("in the user's scope with their highest AI Act tier"), which tells an agent what the rows represent. It is distinguishable from get_application (single record) and portfolio_exposure by the scope framing, though it never names those siblings 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 "in the user's scope" and by the retirement-date filter, which suggests a portfolio-review scenario. However, there is no explicit statement of when to pick this over the sibling tools, and no mention of whether results are paginated or unbounded.

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