Skip to main content
Glama

Describe the Project

describe_project
Read-onlyIdempotent

Call 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations it discloses real behavioral traits: a hard 40,000-byte response cap, a five-entry-per-group journal cap, deliberate omission of role names and human-action links under budget pressure, and role-dependent response bodies (member vs Administrator). Some sentences are opaque rather than clarifying — "That fact grants no authority" and "No member receives it" leave the reader unsure what is being asserted about visibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single run-on block of roughly 200 words that front-loads correctly but then buries the reader in enumeration of individual response fields, including a three-state description of invitation_eligibility that belongs in an output schema. Content about admin counts, journal truncation, and application interviews is interleaved with no structural separation, making it hard to scan.

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 zero parameters, no output schema, and rich annotations, the description carries the return-value burden and does so thoroughly: access level, data boundary, setup stage, counts, journal behavior, and eligibility states are all covered. The only shortfall is that its coverage is uneven and occasionally self-contradictory about who sees the Project purpose.

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

Parameters4/5

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

The tool takes no parameters and the schema is empty with full coverage, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies the tool is context-derived from the caller's identity rather than an argument.

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 opening sentence states a specific verb+resource outcome: it returns the caller's Project access, live tools, and the Applications they can open, and it explicitly partitions work away from describe_application. The rest of the description is a dense field-by-field inventory that dilutes the core statement, so the purpose is clear but not crisply framed.

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

Usage Guidelines5/5

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

"Call this first" establishes ordering explicitly, and it names two alternatives with their selection conditions: describe_application with an application_id to work on an app, and get_setup_journal for the full journal. It also closes the loop with "Call again after changes in the UI," covering re-invocation, which few definitions address.

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