Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_skill_evidence_sweep

Backfills learning-commit evidence across recorded commits using bounded, resumable cursor sweeps; reports skipped reasons and newly activated identity/version records.

Instructions

MANAGER WRITE: backfill learning-commit evidence for every recorded commit.

Bounded and resumable like every other sweep here: pass back next_cursor to continue past a ledger larger than limit. Reports skipped_by_reason (why a window's commit produced no row -- rejected, no selection vocabulary, and so on) and activated (every identity/version this window's evidence pushed across the registry's own two-actor activation gate). A second sweep over an unchanged window records nothing new and activates nothing twice.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum learning commits processed in this call; the default is also the ceiling, and larger values are clamped to it.
cursorNoThe next_cursor returned by a previous sweep, to continue after the last commit it processed; blank starts from the first commit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / cursor / description
      Added value: +"The next_cursor returned by a previous sweep, to continue after the last commit it processed; blank starts from the first commit."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum learning commits processed in this call; the default is also the ceiling, and larger values are clamped to it."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond annotations, the description discloses meaningful behavior: bounded and resumable execution, the skipped_by_reason and activated reporting structure, and the idempotency guarantee that a second sweep over an unchanged window records and activates nothing twice. This is strong behavioral context for a write tool.

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

Conciseness4/5

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

The description is front-loaded with the write classification and core action, then covers resumability and reporting in a compact paragraph. It is appropriately sized, though some phrasing is denser than necessary.

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?

Despite having an output schema, the description usefully explains the meaning of skipped_by_reason and activated, and it covers the idempotency behavior an agent needs before invoking a backfill. Combined with full schema coverage and write annotations, the definition is complete for correct invocation.

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 coverage is 100%, so both limit and cursor are already fully documented. The description reinforces cursor continuation and the limit bound, but does not add syntax or semantics beyond what the schema already provides, making the baseline 3 appropriate.

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 first line states a specific verb and resource: 'backfill learning-commit evidence for every recorded commit.' It clearly distinguishes this bulk sweep from sibling tools such as skill_add_evidence and skill_mine, so an agent can identify the operation without opening the schema.

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 description explains how to continue a sweep via next_cursor and notes that an unchanged window is idempotent, which gives useful operating context. However, it does not explicitly state when to use this tool rather than alternatives like skill_add_evidence or skill_mine, so usage guidance remains largely implied.

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