Skip to main content
Glama

Get one of my projects

project_get
Read-onlyIdempotent

Details of one of your own projects by code (PRJ-YYYY-XXXXXX, from projects_list): summary, status, progress, milestones with state and dates, the latest client-visible updates and attachments (a path only when you actually have access; otherwise the reason). Someone else's or an unknown code returns not found. Free text is wrapped as data.

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": {
      "code": "<code>"
    },
    "name": "project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the return contents, attachment access behavior with fallback reason, not-found behavior for other/unknown projects, and that free text is wrapped as data. These are meaningful behavioral and data-safety details that the annotations alone do not provide.

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?

The description is front-loaded with the core action and code format, then efficiently lists return content and edge behavior. It is dense but has no wasted sentences and reads as a structured contract.

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 read-only single-resource tool with no output schema, the description covers the main return fields, access behavior, and not-found case well. The main gap is the unexplained optional locale parameter, but the overall behavioral picture is complete enough to call the tool correctly.

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 description explains the required code parameter by giving the PRJ format and saying it comes from projects_list, which adds some meaning beyond the schema pattern. However, it does not mention the optional locale parameter or what that enum controls, leaving part of the parameter surface undocumented.

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 states a specific verb and resource: get details of one of your own projects by code. It distinguishes this from list-style siblings by requiring a PRJ code and by noting that the code comes from projects_list, so the agent can tell what this tool returns.

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

Usage Guidelines4/5

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

It gives clear usage context: use a project code obtained from projects_list to retrieve one owned project. It also states that someone else's or unknown code returns not found, though it does not explicitly contrast other retrieval alternatives beyond pointing to projects_list as the code source.

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