Skip to main content
Glama

Describe an Application

describe_application
Read-onlyIdempotent

Call this to work on one Application. When an Administrator is building this Application, calling it tells that Application's Setup you have started. describe_project lists the Application ids. Administrators receive the Application's build context and expected_outcome_revision, its outcome interview while the goal is open, and the next action with its UI route; a published Application with no update in progress answers with its Application page. Members receive a published app they can open: its name, description, URL, and the approved Requests it calls that they can run. When an app is served on its own host, it calls only the Requests it records, plus those listed in calls_without_grant, and confirmation of an action it raises happens on Ekaya's approval page. An id you cannot open answers not_found. Responses are capped at 40,000 bytes.

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": {
      "application_id": "<application_id>"
    },
    "name": "describe_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication UUID, from describe_project's Application list or the person's start message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, yet the description says calling it 'tells that Application's Setup you have started,' which describes a state-changing side effect. This directly contradicts the read-only annotation, even though the rest of the description usefully explains role-dependent responses and the 40,000-byte cap.

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 description is dense and front-loads the core purpose, then layers role-specific behavior. It could be more scannable, but nearly every sentence conveys useful routing or response information.

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 no output schema, the description does substantial work by explaining Administrator and Member response shapes, not_found behavior, hosted-app behavior, and the response size cap. However, the claimed side effect creates ambiguity about what the tool actually changes, which prevents a higher score.

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 description coverage is 100%, and the single application_id parameter is already documented as an Application UUID from describe_project or the start message. The description repeats that describe_project lists ids but adds no new syntax or constraints beyond the schema.

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 identifies the resource (one Application) and distinguishes it from describe_project, which lists Application ids. The opening phrase 'work on one Application' is somewhat vague, but the role-specific return details make the retrieval purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when Administrators and Members should expect different responses and points to describe_project for Application ids. It lacks explicit when-not-to-use guidance, but the usage context is clear enough for an agent to choose it correctly.

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