Skip to main content
Glama
Repo Test Architect

Repo Test Architect

List Project Detection Rules

list_project_detection_rules
Read-onlyIdempotent

Lists deterministic project marker rules and ignored directories used during project detection, clarifying how repositories are identified and which paths are skipped.

Instructions

List deterministic project marker rules and ignored directories used during project detection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
markersYes
fallbackRulesNo
schemaVersionYes
ignoredDirectoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.0
    • removedOutput schema / $id
      Removed value: -"project-detection-rules-v1.schema.json"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / description
      Added value: +"Top-level shape of this artifact. The complete contract is schemas/project-detection-rules-v1.schema.json in the published package."
    • removedOutput schema / properties / fallbackRules / items
      Removed value: -{
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedOutput schema / properties / ignoredDirectories / items
      Removed value: -{
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedOutput schema / properties / markers / items
      Removed value: -{
      -  "additionalProperties": false,
      -  "oneOf": [
      -    {
      -      "required": [
      -        "fileName"
      -      ]
      -    },
      -    {
      -      "required": [
      -        "extension"
      -      ]
      -    },
      -    {
      -      "required": [
      -        "directoryExtension"
      -      ]
      -    }
      -  ],
      -  "properties": {
      -    "directoryExtension": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "ecosystem": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "extension": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "fileName": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "languages": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "minItems": 1,
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "ecosystem",
      -    "languages"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / properties / markers / minItems
      Removed value: -1
    • removedOutput schema / title
      Removed value: -"Project Detection Rules Artifact"
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$id": "project-detection-rules-v1.schema.json",
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "fallbackRules": {
      +      "items": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "ignoredDirectories": {
      +      "items": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "markers": {
      +      "items": {
      +        "additionalProperties": false,
      +        "oneOf": [
      +          {
      +            "required": [
      +              "fileName"
      +            ]
      +          },
      +          {
      +            "required": [
      +              "extension"
      +            ]
      +          },
      +          {
      +            "required": [
      +              "directoryExtension"
      +            ]
      +          }
      +        ],
      +        "properties": {
      +          "directoryExtension": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "ecosystem": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "extension": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "fileName": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "languages": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "minItems": 1,
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "ecosystem",
      +          "languages"
      +        ],
      +        "type": "object"
      +      },
      +      "minItems": 1,
      +      "type": "array"
      +    },
      +    "schemaVersion": {
      +      "const": "project-detection-rules/v1"
      +    }
      +  },
      +  "required": [
      +    "schemaVersion",
      +    "markers",
      +    "ignoredDirectories"
      +  ],
      +  "title": "Project Detection Rules Artifact",
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that the payload consists of marker rules and ignored directories — genuinely useful content context, but no disclosure of rule mutability, precedence, or whether results are configuration-derived.

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 sentence, zero waste, and the two returned data categories are front-loaded. Nothing could be trimmed without losing 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?

For a zero-param, read-only tool with an output schema and rich annotations, the description is nearly sufficient — it says what data is returned. It stops short of explaining how the rules relate to detect_projects' output, which would help an agent chain calls.

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?

Zero parameters, so there is nothing to disambiguate; schema coverage is 100% and additionalProperties is false. Baseline of 4 applies for a parameterless tool.

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 (List) and a concrete resource: deterministic project marker rules plus ignored directories used in project detection. An agent knows exactly what data comes back, though the description never names a sibling (e.g., detect_projects) to differentiate it explicitly.

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 phrase 'used during project detection' implies this is an explanatory/debugging companion to detect_projects, but the description never states when to call it or when to prefer it over detect_projects/analyze_repository. Usage is inferable rather than specified.

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