Skip to main content
Glama

inspect_project

Read-onlyIdempotent

Analyze a CERN GitLab repository to reveal its structure, build system, dependencies, and CI/CD setup in one summary, helping you understand a project's technical stack before changes.

Instructions

Analyze a CERN GitLab repository to understand its structure, build system, and dependencies. Combines functionality of dependency analysis, build config detection, and CI/CD inspection into a single tool. Returns a comprehensive summary of the project's technical stack.

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": {
      "project": "<project>"
    },
    "name": "inspect_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoBranch name, tag, or commit SHA (default: project's default branch)
projectYesProject identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / project / description
      Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')"
  2. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / project / description
      Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"
    • addedInput schema / properties / project / title
      Added value: +"Project"
    • addedInput schema / properties / ref / default
      Added value: +""
    • addedInput schema / properties / ref / title
      Added value: +"Ref"
    • addedInput schema / title
      Added value: +"inspect_project_fnArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "inspect_project_fnDictOutput",
      +  "type": "object"
      +}
  3. First observedv0.1.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety and side-effect profile is fully covered by structured data. The description adds only that the result is a 'comprehensive summary of the technical stack', which is useful framing but not behavior beyond annotations. It says nothing about cost, latency, whether analysis traverses many files or branches, or how deep the inspection goes, which matters for a multi-analysis tool against a remote repository.

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?

Three short sentences, front-loaded with the core action and scope before elaborating on the bundled sub-analyses. Nothing is redundant with the schema or annotations. It could be marginally tighter, but every sentence carries information.

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, the description does not need to specify return fields, and the two-parameter surface is fully documented in the schema, so the remaining burden is scope. The description covers that scope adequately by listing the analyzed dimensions. The only real gap is how this tool relates to the numerous sibling project-inspection tools, which the description does not address.

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 100%, so both 'project' (numeric ID or namespace path) and 'ref' (branch, tag, or commit SHA, defaulting to the default branch) are already documented in the schema. The description contributes no additional meaning about how ref interacts with the analysis, such as whether submodules or CI configs on that ref are resolved. Baseline 3 is appropriate where the schema does all the work.

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?

The description names a specific verb and resource ('Analyze a CERN GitLab repository') and enumerates the concrete things it surfaces: structure, build system, dependencies, CI/CD config. It also signals that it bundles three analyses in one call, which helps distinguish it from narrower siblings like get_project_readme or get_file_content. What is left slightly fuzzy is the boundary against get_project_info, which could plausibly also describe project structure.

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?

Saying it 'combines functionality of dependency analysis, build config detection, and CI/CD inspection into a single tool' implies the use case (one-shot overview instead of several targeted calls), but there is no explicit when-to-use or when-not-to-use guidance. It never names an alternative sibling or states the condition that should send the agent to get_project_info, get_project_readme, or search_code instead. Usage is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.