Skip to main content
Glama

Inspect a project

get_project
Read-onlyIdempotent

Returns an authorized project by exact ID or resolves its name. Ambiguous names return candidates and missing targets return an error without creating replacement projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
project_idNoExact stable project ID. Resolve it first. Never invent an update target.
workspace_idNoWorkspace to inspect or create in. Omit or pass null for Personal. Selection applies only to this call; workspace usage is billed to its owner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 still adds real behavior: ambiguous names return candidates instead of a guess, missing targets error out, and no replacement project is silently created. That is useful non-obvious context beyond the annotations, though return shape is not described.

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?

Two sentences, zero filler, with the primary behavior front-loaded and the edge-case handling (ambiguous, missing) following. Every clause carries information an agent needs.

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 lookup with no output schema and no required parameters, the description covers the outcome cases an agent must handle. What it does not cover, precedence between name and project_id and what fields come back, is modest and partly implied by the 'Returns an authorized project' phrasing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and two parameters carry rich descriptions, but the bare 'name' parameter gets its semantics from the description: it is resolved, and ambiguity yields candidates rather than a pick. That meaningfully extends the schema, though it does not explain precedence when both name and project_id are supplied.

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 ('Returns an authorized project') plus the two lookup modes: exact ID or resolved name. That distinguishes it from list_projects, though it never names a sibling such as get_dynamic_project or get_project_security to disambiguate which getter to call.

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 dual lookup path implies when to use it (you have an ID or a name), and the ambiguity/error behavior tells the agent what to do next. However, it never explicitly says when to prefer this over list_projects or get_dynamic_project, so the routing guidance stays implicit.

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