Skip to main content
Glama
RepoAssay

Repo Test Architect

Collect Project Stats

collect_project_stats
Read-onlyIdempotent

Aggregate coverage, risk, and usage stats from an existing project-audits/v1 artifact for reporting or comparisons. Returns project-stats/v1 without rescanning or writing files.

Instructions

Aggregate coverage, counts, risk and signal distributions, frameworks, and adapter usage from an existing project-audits/v1 artifact. Use this for separate reporting or comparisons; analyze_repository already includes the same stats. Returns project-stats/v1 without rescanning the repository, executing tests, or writing files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectAuditsYesThe project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYes
countsYes
summaryYes
adaptersYes
sourceFilesYes
distributionsYes
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / projectAudits / description
      Previous value: -"A project-audits/v1 artifact."New value: +"The project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "countRecord": {
      +      "additionalProperties": {
      +        "minimum": 0,
      +        "type": "integer"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "$id": "project-stats-v1.schema.json",
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "adapters": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "adapterId": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "projectCount": {
      +            "minimum": 0,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "adapterId",
      +          "projectCount"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "counts": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "blockerCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "coveredButRiskyCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "riskCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "skippedTargetCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "untestedCandidateCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "untestedCandidateCount",
      +        "coveredButRiskyCount",
      +        "skippedTargetCount",
      +        "riskCount",
      +        "blockerCount"
      +      ],
      +      "type": "object"
      +    },
      +    "distributions": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "confidence": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "evidenceKinds": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "evidenceStrengths": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "evidenceUsage": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "evidenceViaUsage": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "riskLevels": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "signals": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "targetKinds": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "testCommands": {
      +          "$ref": "#/$defs/countRecord"
      +        },
      +        "testFrameworks": {
      +          "$ref": "#/$defs/countRecord"
      +        }
      +      },
      +      "required": [
      +        "confidence",
      +        "testFrameworks",
      +        "testCommands",
      +        "targetKinds",
      +        "riskLevels",
      +        "signals",
      +        "evidenceStrengths",
      +        "evidenceKinds",
      +        "evidenceUsage",
      +        "evidenceViaUsage"
      +      ],
      +      "type": "object"
      +    },
      +    "root": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "schemaVersion": {
      +      "const": "project-stats/v1"
      +    },
      +    "sourceFiles": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "audited": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "byLanguage": {
      +          "additionalProperties": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "audited": {
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "total": {
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "unsupported": {
      +                "minimum": 0,
      +                "type": "integer"
      +              }
      +            },
      +            "required": [
      +              "total",
      +              "audited",
      +              "unsupported"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "object"
      +        },
      +        "total": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "unsupported": {
      +          "minimum": 0,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "total",
      +        "audited",
      +        "unsupported",
      +        "byLanguage"
      +      ],
      +      "type": "object"
      +    },
      +    "summary": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "auditCoverage": {
      +          "enum": [
      +            "complete",
      +            "partial",
      +            "none"
      +          ]
      +        },
      +        "auditedProjectCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "projectCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "unsupportedProjectCount": {
      +          "minimum": 0,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "projectCount",
      +        "auditedProjectCount",
      +        "unsupportedProjectCount",
      +        "auditCoverage"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "schemaVersion",
      +    "root",
      +    "summary",
      +    "sourceFiles",
      +    "counts",
      +    "distributions",
      +    "adapters"
      +  ],
      +  "title": "Project Stats Artifact",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description still adds real behavioral value by stating the tool does NOT rescan the repository, execute tests, or write files, and that it returns project-stats/v1, which clarifies cost profile and side-effect surface beyond the annotations.

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?

Three compact sentences, each earning its place: purpose/inputs, usage routing, and behavioral guarantees. Front-loaded with the core action and free of filler.

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

Completeness5/5

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

With an output schema present, return values need no elaboration, yet the description still names the output type (project-stats/v1). Source artifact, usage context, and non-side-effect guarantees are all covered, leaving no gap an agent needs to call it correctly.

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?

Only one parameter with 100% schema description coverage, so the schema already documents that it takes the project-audits/v1 object rather than a file path. The description's mention of 'existing project-audits/v1 artifact' adds no syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (aggregate) plus the resource and exact field set (coverage, counts, risk/signal distributions, frameworks, adapter usage) sourced from a project-audits/v1 artifact. It clearly distinguishes itself from sibling analyze_repository and audit_projects by naming the source artifact type.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('separate reporting or comparisons') and names the overlapping alternative ('analyze_repository already includes the same stats'), giving the agent a routing decision rule. This is the exact when/when-not/alternative structure the top score requires.

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