Skip to main content
Glama

get_project

Read-onlyIdempotent

Retrieve full details for a single project by ID or title, including members, admins, boards with open/done/overdue counts, settings, and labels.

Instructions

Full detail for one project (id or title): members, admins, boards with per-board open/done/overdue counts, settings, labels.

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": {
      "project": "<project>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds the returned content set, but that is largely duplicated by the existing output schema, and it says nothing about not-found handling, permission scoping, or title ambiguity, which are the real behavioral risks for a lookup by name.

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

Conciseness5/5

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

A single front-loaded sentence with a colon-delimited enumeration; every element (identifier forms, member/admin lists, per-board counts, settings, labels) conveys what the caller will receive, and there is no filler.

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 rich annotations and an output schema present, the description only needs to cover input form and scope, and it does both. The remaining gap is ambiguity/error behavior for title lookups, which is minor for a read-only detail tool.

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?

Schema coverage is 0% for the single "project" parameter, so the description must compensate, and it does by specifying the accepted forms: id or title. It stops short of explaining what happens when a title matches multiple projects, which is the main ambiguity an agent would face.

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?

States a specific verb+resource ("Full detail for one project") and enumerates what the detail contains: members, admins, boards with per-board counts, settings, labels. "Full detail" implicitly contrasts with the summary/listing siblings, but no sibling is named, so differentiation is inferred rather than stated.

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?

Usage is only implied by the phrase "Full detail for one project" — an agent can guess this is for drilling into a single project rather than scanning, but there is no explicit when-to-use, no named alternative (list_projects, get_projects_summary), and no preconditions such as needing a prior lookup to obtain an id.

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