Skip to main content
Glama

Get a project

get_project
Read-onlyIdempotent

One project of list_projects by id, with its client and the project tasks that take time.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the project

Output Schema

NameRequiredDescriptionDefault
idYes
feeNo
nameYes
tasksYes
billingNo
archivedNo
currencyNo
client_idYes
client_nameYes
hourly_rateNo
expense_markupNoA percentage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds genuine value by disclosing the payload shape: the project comes back with its client and its time-bearing tasks, which implies extra related data is joined in. It does not mention behavior on a missing/invalid id.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; it leads with what is returned and the lookup key. Minor cost from the indirect "One project of list_projects" construction, which takes a beat longer to parse than "Get a single project."

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 an output schema present and rich annotations, the description only needs to route and set expectations, and it does that plus notes the joined client/tasks. The phrase "tasks that take time" is left slightly cryptic, and there is no mention of not-found behavior for a single-item lookup.

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?

Only one parameter, documented at 100% schema coverage with uuid format, so the schema fully carries the semantics. The description restates "by `id`" and adds nothing about format or lookup behavior, which is the expected baseline when the schema is complete.

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 resource (a single project) and explicitly anchors it as the singular counterpart of list_projects, selecting it by `id`. That framing lets an agent distinguish it from list_projects without opening either schema, though the phrasing "One project of list_projects" is slightly awkward.

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: fetch one project when you already have its id, rather than enumerating via list_projects. There is no explicit when-not guidance (e.g., what to do if the id is unknown, or whether to use list_projects to discover ids), so the agent must infer the boundary.

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