Skip to main content
Glama

Get a project

naut_get_project
Read-only

One project with its team. Accepts an id or a slug. Costs 5 credits.

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": "naut_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProject id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 this a safe, closed-world read. The description adds a genuinely new behavioral fact the annotations do not cover: the call costs 5 credits, which lets an agent budget calls. It does not say what happens when the id resolves to nothing, which is the remaining gap.

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?

Three short sentences, each carrying a distinct fact: return contents, accepted input, and cost. Nothing is padded and the most useful information leads.

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 full schema coverage and a safety annotation, the description covers return shape, input form, and cost. Only the not-found behavior is left unstated, which is a minor omission at this complexity.

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?

Schema coverage is 100% and the single property is already documented as "Project id or slug," so "Accepts an id or a slug" restates the schema rather than extending it. Baseline 3 applies; no slug format or lookup-precedence detail is added.

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?

"One project with its team" identifies the resource (project) and its scope (single record plus related team), which separates it from the plural search siblings. It stops short of an explicit verb, but the title and the phrase together leave no ambiguity about what comes back.

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?

"Accepts an id or a slug" implies this is the direct-lookup path once you already have an identifier, so usage is inferable. It never states when to prefer this over naut_search_projects or what to do when you lack an id, so nothing is explicit.

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