Skip to main content
Glama

get_project_info

Retrieve project-level information including name, path, start and end dates, and available scenarios for the active OmniPlan document.

Instructions

Return project-level info for the front document.

Returns: JSON {name, path, start_date, end_date, scenarios}. path comes from the JXA SDEF surface (omniJS doesn't expose it). start_date and end_date are the actual scenario's computed bounds (ISO YYYY-MM-DD). scenarios is ["Actual", ...proj.baselineNames] — the active scenario followed by every baseline scenario name defined on the project. The order matches OmniPlan's own baseline list; "Actual" is the conventional name for the active scenario (proj.actual).

omniJS surface gaps surfaced during implementation (probed 2026-05-01 against OmniPlan 4.10.2):

  • proj.startDate is undefined; date lives on actual.startDate.

  • actual.currency accepts a write inline but does NOT persist across JXA calls (same trap as constraint dates) — omitted from the response shape rather than returning a stale value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully bears the burden of transparency. It details the return format, data sources (JXA SDEF surface vs omniJS), and known implementation quirks like date and currency persistence issues, offering deep behavioral insight.

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

Conciseness3/5

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

The description is front-loaded with the main purpose but includes extensive implementation details and surface gap notes. While each sentence adds value, the length could be reduced for quick consumption.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema provided in the input, the description fully specifies the return shape (JSON fields and their meanings) including edge cases and known bugs, making the tool's behavior completely understandable.

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?

No parameters exist, and schema coverage is 100%. Baseline for zero-parameter tools is 4; the description adds no redundant parameter info, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Return project-level info for the front document,' specifying the verb (return), resource (project-level info), and scope (front document). This distinguishes it from siblings like get_task or list_documents.

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?

The description implies usage for obtaining project-level details but does not explicitly contrast with alternatives or advise when not to use it. No exclusions or sibling references are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johntrandall/omniplan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server