Skip to main content
Glama

get_application

Read-only

Retrieves one application's governance record by ID, covering owner, lifecycle, data, AI use cases, and assessments for review.

Instructions

Full record of one application: owner, lifecycle, data, AI use cases and their assessments.

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": {
      "app_id": "<app_id>"
    },
    "name": "get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. The description adds value by disclosing what the record contains (owner, lifecycle, data, AI use cases and assessments), but says nothing about behavior when app_id is unknown, access restrictions, or record size.

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?

A single compact sentence with the core purpose front-loaded and no filler. The trailing field enumeration is scannable and earns its place as a preview of record contents.

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, so return-value specifics need not be spelled out, though the description partly overlaps it. The main gap is the undocumented identifier parameter and the absence of any failure or availability behavior for a lookup tool.

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

Parameters2/5

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

Schema description coverage is 0% and the description contributes nothing about app_id — not its format, whether it is an internal ID or a name, or where to obtain it. With a single undocumented parameter the description should compensate, but it does not.

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+resource ('Full record of one application') and enumerates the record's content areas (owner, lifecycle, data, AI use cases and assessments). The singular 'one application' implicitly separates it from list_applications, but no sibling is named 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 only implied: fetching the detail record for a single application, presumably when you already have its identifier. There is no explicit when-to-use, no guidance on how this relates to list_applications or portfolio_exposure, and no prerequisites stated.

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