Describe an Application
describe_applicationCall 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
| Name | Required | Description | Default |
|---|---|---|---|
| application_id | Yes | Application UUID, from describe_project's Application list or the person's start message. |