Skip to main content
Glama

Get project

get_project
Read-onlyIdempotent

Fetch a single project by its UUID. Returns 404 if the project is not in the caller's org.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject UUID

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
slugYes
orgIdYes
statusYes
scmRepoYes
trackerYes
scmOwnerYes
autoMergeYes
createdAtYes
issueCodeYes
siteTemplateYes
provisionedByNo
trackerTeamIdYes
llmConnectorIdYes
scmConnectorIdYes
trackerProjectIdYes
trackerConnectorIdYes
missingConnectorKindsNo
defaultSandboxTemplateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / provisionedBy
      Added value: +{
      +  "enum": [
      +    "ship",
      +    "owner"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / siteTemplate
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "orgId",
      -  "slug",
      -  "name",
      -  "status",
      -  "tracker",
      -  "trackerConnectorId",
      -  "trackerTeamId",
      -  "trackerProjectId",
      -  "scmConnectorId",
      -  "scmOwner",
      -  "scmRepo",
      -  "llmConnectorId",
      -  "autoMerge",
      -  "issueCode",
      -  "defaultSandboxTemplateId",
      -  "createdAt"
      -]New value: +[
      +  "id",
      +  "orgId",
      +  "slug",
      +  "name",
      +  "status",
      +  "tracker",
      +  "trackerConnectorId",
      +  "trackerTeamId",
      +  "trackerProjectId",
      +  "scmConnectorId",
      +  "scmOwner",
      +  "scmRepo",
      +  "llmConnectorId",
      +  "autoMerge",
      +  "issueCode",
      +  "defaultSandboxTemplateId",
      +  "siteTemplate",
      +  "createdAt"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / tracker / enum
      Previous value: -[
      -  "linear",
      -  "github-issues",
      -  "none"
      -]New value: +[
      +  "linear",
      +  "github-issues",
      +  "jira",
      +  "none"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds real context beyond them: a not-found path (404) and an authorization boundary (projects outside the caller's org surface as not-found). It does not discuss pagination or response shape, but the output schema covers returns.

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?

Two short sentences, zero filler, with the core action front-loaded and the failure/scope caveat second. Nothing could be removed without losing information.

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?

For a one-parameter read tool with full schema coverage, an output schema, and rich annotations, the description covers the essentials including the org-scoping failure mode. Only minor gaps remain, such as whether a malformed UUID yields a validation error versus a 404.

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

Parameters3/5

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

With a single parameter at 100% schema description coverage, the schema already documents projectId as a UUID with a validation pattern. The description reinforces that the key is a UUID but adds no format, sourcing, or error nuance beyond that, so the baseline applies.

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 and resource ("Fetch a single project") plus the lookup key (UUID), which separates it from multi-entity siblings like get_project_transfer or get_agent_run. It stops short of explicitly naming a sibling to contrast against, so it lands just below the top mark.

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: the phrase "a single project by its UUID" signals this is a point lookup rather than a listing or search. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to update_project or get_project_transfer for adjacent needs.

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.