Describe the Project
describe_projectCall this first. It answers your Project access, live tools and the Applications you can open; where describe_application is offered, call it with one's application_id to work on it. Members receive their effective MCP level, data boundary, and how to request more access; source Role names may be omitted to fit the budget, so ask an Administrator for the full list. Administrators receive the current setup stage and next action with its UI route. Administrators also receive datasource, Data Access Point, and approved Request counts, and live invitation_eligibility for seat-taking invitations: restricted with team_required when another User needs Ekaya Team, eligible when one is available, or unavailable when Central did not answer. That fact grants no authority. Responses are capped at 40,000 bytes. The journal shows at most five entries per group, prioritizing open, unblocked work; human-action links may be omitted under budget pressure. Retrieve the full journal with get_setup_journal when offered or the Setup journal UI. Application interviews are provided by describe_application where it is offered. The Project purpose is the overview saved in Project Knowledge when present. No member receives it. Call again after changes in the UI.
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": "describe_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||