Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ecosystem_scan_periodic

Run incremental or full ecosystem scans to find relevant repositories, skip recently scanned projects, apply owner or keyword filters, archive stale repos, and record each run for audit.

Instructions

Run an incremental or full ecosystem scan via the scanner service.

Compared to ecosystem_scan, this tool:

  • skips repos last_scanned_at < 7 days (incremental strategy only)

  • applies secondary owner / keyword filters

  • marks repos pushed > 365 days ago as is_archived=True

  • records every run as an EcosystemScanRun for audit

Queries and filters come from the built-in query set and ECOSYSTEM_* environment variables, not the project's ecosystem settings. For a settings-driven scan with a diff and a new-repo alert, use ecosystem_index_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional human-readable note attached to the ScanRun.
strategyNo"incremental" (default; skips repos scanned in the last 7 days) or "full" (rescans all). "topic" and "trending" are accepted but run the same query set as "full"; unknown values fall back to "incremental".incremental
min_starsNoMinimum star threshold for inclusion (default 1000).
triggered_byNoFree-form label recorded on the ScanRun (default "manual").manual

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / min_stars / description
      Previous value: -"Minimum star threshold for inclusion (default 1000 for Stage C)."New value: +"Minimum star threshold for inclusion (default 1000)."
    • changedInput schema / properties / strategy / description
      Previous value: -"\"incremental\" (skip recent), \"full\" (rescan all),\n\"topic\" (topic-only), \"trending\" (trending repos only)."New value: +"\"incremental\" (default; skips repos scanned in the last\n7 days) or \"full\" (rescans all). \"topic\" and \"trending\" are\naccepted but run the same query set as \"full\"; unknown values\nfall back to \"incremental\"."
    • changedInput schema / properties / triggered_by / description
      Previous value: -"\"manual\" or \"cron\" — recorded on the ScanRun."New value: +"Free-form label recorded on the ScanRun (default \"manual\")."
  2. First observedv1.9.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses incremental vs full behavior, the 7-day skip rule, secondary filters, archived marking, and audit recording. It omits permissions, authentication requirements, rate limits, and failure modes, which keeps it from being fully transparent for a service-backed mutation-adjacent scan.

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?

The description is front-loaded with the core action, uses a compact bullet list for sibling differentiation, and ends with the routing alternative. Every sentence contributes useful selection or behavioral 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?

An output schema exists, so return values need not be explained. The description covers selection criteria, configuration source, and side effects well, but for a scan tool with audit side effects and no annotations, it leaves permissions and operational constraints unstated.

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 the schema already documents all four parameters thoroughly. The description adds some context around the strategy's skip behavior but does not provide syntax or semantics beyond what is already in the parameter descriptions.

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?

The description states a specific verb and resource: 'Run an incremental or full ecosystem scan via the scanner service.' It differentiates this tool from both ecosystem_scan and ecosystem_index_update by listing distinctive behaviors and configuration sources, so an agent can identify it without opening schemas.

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?

It explicitly contrasts this tool with ecosystem_scan and names ecosystem_index_update as the alternative for settings-driven scans with a diff and new-repo alert. The configuration source distinction (built-in query set and ECOSYSTEM_* environment variables, not project settings) gives a clear condition for choosing one over the other.

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

Deploy Server

Other Tools