Skip to main content
Glama

Alignment gaps

alignment_gaps
Read-onlyIdempotent

Detect Bloom's-level mismatches between objectives, assessments, and activities, including items below objectives, unreached or untargeted objectives, unassessed items, and missing levels.

Instructions

Where assessment and objectives disagree by Bloom's level, for one module's declared objectives or the whole design: items below the level of the objective they assess (and by how many levels), objectives no item reaches at their level, objectives no activity targets, items that assess no objective, and objectives or items with no level. Empty lists mean no gap of that kind. Run it after an objective's level changes to see what the change left behind.

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

Input Schema

NameRequiredDescriptionDefault
refNoA commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both.
branchNoThe branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both.
moduleNoA module's id, to check its declared objectives; the whole design when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description's job is lighter. It adds genuinely useful behavior beyond them: the empty-list semantics ('Empty lists mean no gap of that kind'), which is the main ambiguity for a diagnostic tool with no output schema, plus the explicit set of gap kinds reported.

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?

Front-loaded with the purpose, then the gap enumeration, then the empty-list rule and the usage trigger. The middle list is long and chained with 'and', but every element names a distinct outcome, and the final sentence earns its place as a trigger.

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-required-parameter read tool with no output schema, the definition covers scope, the taxonomy of results, empty-result meaning, and a usage moment. The only minor gap is that it does not hint at result shape (grouped per objective vs flat lists), which an agent must inspect at runtime.

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 ref, branch and module are already fully documented in the schema, and the description only reinforces module scope ('the whole design when left out'). It adds nothing about ref/branch, 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?

The description states a specific verb+resource ('where assessment and objectives disagree by Bloom's level') and then enumerates the exact gap categories returned (items below their objective's level, objectives no item reaches, objectives no activity targets, orphan items, unlevelled items). That specificity makes it distinguishable from coverage-style siblings such as module_coverage and course_coverage.

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 gives a concrete trigger ('Run it after an objective's level changes to see what the change left behind') and states the scope choice between a single module's declared objectives and the whole design. It does not name an alternative tool or say when not to use this one, which keeps it short of a 5.

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