Skip to main content
Glama

project_inspect

Read-only

Parse and validate an .rnrproj file and check artifact membership against the reference index to catch project inconsistencies.

Instructions

Parse and validate an .rnrproj, including artifact membership against the reference index.

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": {
      "path": "<path>"
    },
    "name": "project_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
guidNo
nameNo
pathNo
errorNo
modelNo
validNo
sha256No
artifactsNo
diagnosticsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful scope (validation includes artifact membership against the reference index), but says nothing about failure modes, whether it errors on a malformed project or returns diagnostics, or the dependency on index freshness. Return details are covered by the existing output schema.

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?

One tightly packed sentence with the object of the operation front and center. No filler, no restatement of the tool name, and the second clause adds real scope rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema removes the need to describe return values, and annotations cover the safety profile. However, for a two-parameter tool with zero schema descriptions, the definition leaves an agent guessing about root and about what 'validate' actually reports, so it is only minimally sufficient.

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

Parameters2/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 the parameter meaning and it largely fails. The path parameter is at least implied by the mention of .rnrproj files, but the optional root parameter is never explained, and no format, path-style, or relative-vs-absolute expectations are given.

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 specific verbs (parse, validate) and a specific resource (.rnrproj), plus the extra scope of artifact-membership checking against the reference index. It is distinguishable from solution_inspect or build_project, though it never names a sibling to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or prerequisite guidance. An agent is left to infer that this is the pre-flight validation step before build_project or project_update, and nothing tells it whether the reference index must already be populated for the membership check to be meaningful.

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