Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_skill_add_evidence

Append accepted or negative manager evidence to a skill version, or resolve an unresolved negative source by recording the required reason note.

Instructions

MANAGER WRITE: append one MANAGER evidence entry to a skill version.

CLOSED VOCABULARIES -- a guess is refused before a turn is spent: outcome accepted | negative actor_id ^[a-z][a-z0-9_.-]{0,127}$, and it may NOT contain the reserved role tokens worker, reviewer, coordinator, agent or owner. Those name a DERIVED identity read off a task card's own runner and can never be typed here.

Two spellings of one manager are ONE actor: identities are compared in their canonical form, so manager.claude.7e and claude_manager_7e do not make an activation independent. Genuinely independent evidence comes from a card: it is appended automatically when a decision is recorded on a card the skill was injected into, and can be filed for one card at a time through the task-derived path.

When resolve_negative_source is set, no row is appended: the one unresolved negative row with that source is marked resolved instead, with note as the REQUIRED reason (source and outcome are ignored).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identity": "<identity>",
      "version": "<version>",
      "source": "<source>",
      "outcome": "<outcome>",
      "actor_id": "<actor_id>"
    },
    "name": "aiworkhub_manager_skill_add_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoFree-text note stored with the entry; default empty. It is the required reason when resolve_negative_source is set.
sourceYesNon-blank evidence anchor the entry rests on, for example a task card id; ignored when resolve_negative_source is set.
outcomeYesResult the entry records, accepted or negative; ignored when resolve_negative_source is set.
versionYesVersion of that skill identity the evidence applies to.
actor_idYesManager identity filing the entry, ^[a-z][a-z0-9_.-]{0,127}$ without the reserved tokens worker, reviewer, coordinator, agent or owner.
identityYesIdentity of the skill to add evidence to, as shown by aiworkhub_manager_skill_usage.
resolve_negative_sourceNoSource of the unresolved negative row to mark resolved, with note as the required reason, instead of appending a row; default empty appends.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.12.67
    • addedInput schema / properties / actor_id / description
      Added value: +"Manager identity filing the entry, ^[a-z][a-z0-9_.-]{0,127}$ without the reserved tokens worker, reviewer, coordinator, agent or owner."
    • addedInput schema / properties / identity / description
      Added value: +"Identity of the skill to add evidence to, as shown by aiworkhub_manager_skill_usage."
    • addedInput schema / properties / note / description
      Added value: +"Free-text note stored with the entry; default empty. It is the required reason when resolve_negative_source is set."
    • addedInput schema / properties / outcome / description
      Added value: +"Result the entry records, accepted or negative; ignored when resolve_negative_source is set."
    • addedInput schema / properties / resolve_negative_source / description
      Added value: +"Source of the unresolved negative row to mark resolved, with note as the required reason, instead of appending a row; default empty appends."
    • addedInput schema / properties / source / description
      Added value: +"Non-blank evidence anchor the entry rests on, for example a task card id; ignored when resolve_negative_source is set."
    • addedInput schema / properties / version / description
      Added value: +"Version of that skill identity the evidence applies to."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare write semantics (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's added value is the recalcitrant edge cases: identity canonicalization means two spellings are one actor, and setting resolve_negative_source appends nothing and instead resolves a row with note as the required reason. That is useful behavior beyond the annotations, though it doesn't cover failure modes or authorization. Actually that's substantive enough for a 5.

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 operation, then uses headed blocks for the closed vocabularies and the resolve mode. It is slightly long, with the canonical-form paragraph repeating the actor rule, but each section carries information an agent would otherwise have to discover through a failed call.

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?

Given seven parameters, a required-note conditional, and an alternative non-appending mode, the description covers the full call contract. An output schema exists, so return-value explanation is correctly omitted.

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?

Schema coverage is 100%, so the schema already documents each field. The description nevertheless adds meaning: it states that note becomes the required reason under resolve_negative_source, that source and outcome are ignored in that mode, and that actor_id rejects the reserved role tokens worker, reviewer, coordinator, agent, and owner.

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 opens with a specific verb and resource: 'append one MANAGER evidence entry to a skill version.' It also distinguishes the manager-authored path from the task-derived path that files evidence automatically for a card, which no sibling name alone conveys.

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

Usage Guidelines4/5

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

It explains the closed vocabularies for outcome and actor_id, warns that guessed identities are refused, and clarifies that genuinely independent evidence should come from a card rather than being typed here. It stops short of explicitly naming which sibling tool to use for the task-derived path, which keeps it from a 5.

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