Skip to main content
Glama

project_get

Read-onlyIdempotent

Project details, app info, project record, settings, metadata — fetch one project by id, subdomain, or "default". Returns the full project record. When the project's editors have saved context (see project_context), it is included as project_context: instructions, design principles and note topics, labelled as project data.

Example:

{ "project_id": "my-saas" }
// or
{ "project_id": "default" }

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_id": "<project_id>"
    },
    "name": "project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real behavioral context beyond that: the full project record is returned, and editor-saved context appears as project_context with instructions, design principles and note topics labelled as project data — a meaningful disclosure about payload shape.

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 lead sentence is keyword-stuffed with near-synonyms ('Project details, app info, project record, settings, metadata') that do not each earn their place. The core statement and the project_context note are well front-loaded, but the example block mostly duplicates what the schema already says.

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 single-parameter read tool with an output schema and full annotation coverage, the description covers what an agent needs: identifier resolution, the 'default' shortcut, and the conditional project_context field. Return-value detail is legitimately delegated to the output schema.

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?

The schema already documents project_id at 100% coverage including UUID/subdomain/slug resolution and the multi-project error case. The description's JSON example merely restates 'default' and a slug value, adding no syntax or resolution meaning beyond the schema. Baseline 3 applies where the schema does the heavy lifting.

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 concrete verb and resource: 'fetch one project by id, subdomain, or "default"' and 'Returns the full project record.' That distinguishes it from a list-style sibling like project_list. It stops short of naming an alternative explicitly, which keeps it at 4 rather than 5.

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 implied rather than stated — an agent infers this is for reading a single known project. The 'default' fallback for single-project accounts is a useful contextual rule, but there is no explicit when-not-to-use guidance or named alternative (e.g. project_docs, project_patch) despite a large sibling set.

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