Skip to main content
Glama

Get project

get_project
Read-onlyIdempotent

Inspect an authorized project with bounded pages of datasets, input assets, output artifacts, jobs and runs. Each section reports its own availability and pagination; unavailable sections do not imply empty results.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "project_id": "returned-project_id"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
project_idYes

Output Schema

NameRequiredDescriptionDefault
projectYes
relatedYes
warningsYes
context_completeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value beyond them: results are 'bounded pages', each section reports its own availability and pagination, and 'unavailable sections do not imply empty results' — a non-obvious semantic caveat that prevents misreading partial responses.

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?

Two tightly written sentences with the resource and scope front-loaded and no filler. The second sentence adds a caveat rather than restating the first.

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?

An output schema exists, so return values needn't be explained, and the description covers the composite-section behavior and partial-availability semantics that matter for interpreting output. The remaining gap is parameter-level detail for limit/offset/project_id, which the low schema coverage leaves undocumented.

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 description coverage is 0%, so the description must carry parameter meaning and largely does not: limit, offset and project_id are never explained, and only 'bounded pages' hints at pagination. The schema does supply defaults, min/max bounds and an example object, which partially offsets the gap.

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 ('Inspect an authorized project') and enumerates the composite sections returned (datasets, input assets, output artifacts, jobs, runs), so the agent knows this is an aggregate project view rather than a single-resource fetch. It does not explicitly distinguish itself from siblings like list_projects or get_dataset, leaving differentiation to inference.

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?

The word 'authorized' implies a permission prerequisite, and the enumeration of sections implies when this tool is appropriate (a broad project overview). However, there is no explicit when-to-use versus when-not guidance and no named alternative for narrower lookups, so usage must be inferred from the section list.

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