Skip to main content
Glama

My apps and licences

my_apps_list
Read-onlyIdempotent

Your own Barmaan apps, subscriptions and licences: reference, kind, product, plan, status (active, expiring, grace, expired, suspended, cancelled, pending, scheduled), days left, dates, seats, domains and how many files you can download. Filter by kind or status, search with query, page with next_cursor. The licence key itself is never returned. An empty list means nothing has been added to your account yet.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
sortNo
limitNo
queryNoMatches title, plan, product or domain.
cursorNoValue of next_cursor from the previous page.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description doesn't need to restate that. It does add genuinely useful behavior beyond the annotations: the licence key is never returned (a redaction guarantee) and an empty list has a specific meaning, which prevents misreading a zero-result response.

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 resource and scope are front-loaded, followed by filtering/paging mechanics and two short clarifying sentences. The middle field enumeration is dense but earns its place because no output schema exists; overall it is efficient with no 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?

With six optional parameters and no output schema, the description compensates well by describing returned fields and the empty-result case, and it closes the loop on sensitive data (licence key never returned). The gaps are sort and limit semantics plus explicit routing to the single-app sibling, which keep it short of full completeness.

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 only 33%, so the description should carry more weight: it mentions kind, status, query and cursor-based paging, but never explains sort or limit, which are the two undocumented parameters. The long status enumeration appears to describe result values rather than filter values (the schema's status enum is only active/expiring/expired/all), which could mislead an agent about accepted filter inputs.

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 description names the resource precisely ("Your own Barmaan apps, subscriptions and licences") and enumerates what each entry contains (reference, kind, product, plan, status, seats, domains, download allowance), so an agent knows this is a personal-scope listing tool. It does not explicitly distinguish itself from singular siblings such as my_app_get or my_app_download_link, leaving that inference to the agent.

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 rather than stated: it explains that you can filter by kind or status, search with query and paginate with next_cursor, and it clarifies that an empty list means no records exist rather than an error. There is no explicit when-to-use guidance versus my_app_get (single app) or the other my_* list tools, and no stated 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