Skip to main content
Glama

project_status

Inspect a project folder to report missing, changed, or new datasheet copies and problems per part and document. It flags newer releases, LLM client restarts, or sync issues without changing files.

Instructions

The parts and documents of the user project, and the state of the copies in the project folder: missing or changed copies, new files, problems. It changes nothing. Gives one line for each part (MPN, manufacturer, base part) and one line for each document (reference, role, file). The first line of a datasheet of more parts gives these parts (variants); the next lines of the document do not. A first line can tell about a newer release or a necessary restart of the LLM client, or about the team server (a failed sync, a conflict): tell the user.

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

Input Schema

NameRequiredDescriptionDefault
pathNoA folder of the user project (default: the working folder of the server). The project file datasheet-lens.toml is in it or in a parent folder.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden itself and does so with 'It changes nothing', which is an unambiguous read-only declaration. It also discloses the output shape (one line per part with MPN/manufacturer/base part, one line per document with reference/role/file) and instructs the agent to relay first-line signals about a newer release, a required LLM client restart, or a team-server sync failure/conflict to the user. Remaining gaps: no mention of error behavior if the project file is absent, and no cost/latency expectation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is broken across arbitrary line wraps, front-loads an awkward noun phrase instead of an action, and contains a near-incomprehensible passage about the first line of a multi-part datasheet giving variants while later lines do not. Useful content is present but the structure and phrasing force the agent to reconstruct the meaning.

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?

An output schema exists, so the description is not obliged to enumerate return values, yet it spends several sentences doing so (partially redundant) while omitting the more valuable routing information versus sibling tools. Read-only semantics, project-file dependency and notification handling are covered, so it is adequate but not complete for a tool sitting among many overlapping siblings.

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% and the sole 'path' parameter is fully documented in the schema, including the default working folder and the datasheet-lens.toml lookup in a parent folder. The description adds nothing about the parameter, so the baseline 3 applies.

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 states a concrete scope: the parts and documents of the user project plus the state of their copies (missing, changed, new files, problems), and it commits to a read-only nature. The scope is clear, but it is expressed as a noun phrase rather than a verb+resource, and it never distinguishes itself from siblings such as list_parts, list_documents, project_check or project_availability that read overlapping data.

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 explicit when-to-use statement and no naming of alternatives, even though five siblings (list_parts, list_documents, project_check, project_availability, project_sync) overlap with this output. The agent must infer from 'state of the copies ... problems' that this is the diagnostic/health-check tool rather than a plain listing tool.

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