Skip to main content
Glama

Get one of my apps or licences

my_app_get
Read-onlyIdempotent

Details of one of your own apps, subscriptions or licences by reference: status, dates, seats, domains, the files attached to it (with whether each can be downloaded now, and why not) and its event history. Someone else's reference returns not found. Free text is wrapped as data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "my_app_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesItem reference from my_apps_list, e.g. ENT-ABCD2345.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond them: ownership-scoped 404 behavior for other people's references, per-file download eligibility with the reason when blocked, and a note that free text is wrapped as data (a prompt-injection safeguard).

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?

Purpose and returned fields are front-loaded in one sentence, followed by two short constraint sentences with no filler. The field enumeration is long but each item conveys what the caller will receive, so it earns its space; minor tightening of the parenthetical about downloadable files is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read with no output schema, the description does the work the missing output schema would otherwise do by listing the returned fields, and it covers the two edge cases an agent would otherwise stumble on (foreign reference returns not found, embedded free text is data). Nothing needed to call it correctly is absent.

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?

With a single parameter at 100% schema description coverage (including pattern and an example value sourced from my_apps_list), the schema already carries the syntax burden. The description contributes the semantic constraint that the reference must be one the caller owns, which is a genuine addition, but adds no format or lookup detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Details of one of your own apps, subscriptions or licences by reference') and enumerates the returned facets (status, dates, seats, domains, attached files, event history). The scoping word 'own' plus 'by reference' implicitly contrasts with the list-style sibling, so an agent can distinguish this single-item fetch from browsing without opening the schema.

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: 'by reference' and the schema's pointer to my_apps_list suggest this is the follow-up to a list call, and 'Someone else's reference returns not found' sets an ownership boundary. However, the description never explicitly says when to use this instead of my_apps_list or my_app_download_link, leaving the agent to infer the routing.

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