Skip to main content
Glama

Retroactive Awards Preview

retroactive_awards_preview
Read-only

Simulate missing edubits to award for a test within a date range and preview retroactive award totals and eligible counts before applying changes.

Instructions

(Admin) Simula los edubits que faltan acreditar de un test en un rango (ISO UTC, p. ej. 2026-08-01T00:00:00Z).

La deuda real es la suma de awardedAmount > 0 en eligible; eligibleCount incluye nota 0 y topados.

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": {
      "test_id": "<test_id>",
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "retroactive_awards_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes
to_dateYes
from_dateYes
coins_per_question_overrideNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with a simulation that credits nothing. Beyond that, it adds real behavioral context: how the true debt figure is computed (sum of awardedAmount > 0 within `eligible`) and the non-obvious fact that eligibleCount includes zero grades and capped students.

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?

Two short sentences, front-loaded with the admin marker and the core action, with no filler. The second sentence is dense but each clause carries semantic weight about result interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 structure needn't be explained, and the description still clarifies the meaning of two key result fields. The gap is the undocumented override parameter and the absence of any preview-before-execute workflow guidance for a tool that is clearly one half of a paired operation.

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 0%, so the description must carry parameter meaning. It adds the ISO-UTC format with a concrete example for from_date/to_date and ties test_id to the tested resource, but says nothing about coins_per_question_override, which is the parameter most likely to change results.

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?

The description names a specific verb and resource: it simulates the edubits still owed for a test over a date range, and marks the tool as admin-only. It does not explicitly name the write-side sibling retroactive_awards_execute, so differentiation relies on the name/preview-vs-execute cue rather than on the text.

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?

"Simula" implies a non-persisting preview, which implicitly contrasts with the execute sibling, and "(Admin)" signals the privilege context. However, there is no explicit statement of when to use this versus executing, and no stated prerequisite that a preview should precede the real run.

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