Skip to main content
Glama

Retroactive Awards Execute

retroactive_awards_execute
Destructive

Credits pending Edubits for a test within a date range to Edubank, skipping already awarded attempts and requesting confirmation before execution.

Instructions

(Admin) Acredita en edubank los edubits pendientes de un test en un rango. Pide confirmación.

Recomendado: rangos de un intento ([finishedAt - 1 s, finishedAt + 1 s]) en orden cronológico, así se respeta el tope por alumno. Los ya acreditados se saltan solos.

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_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes
to_dateYes
from_dateYes
confirm_tokenNo
coins_per_question_overrideNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, and the description adds real behavior: confirmation is requested, already-credited entries are skipped, and per-student caps constrain batching. The note that already-credited rows are skipped sits in mild tension with idempotentHint=false, but it is a partial-cap semantics caveat rather than a direct contradiction.

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 blocks, front-loaded with the action and the confirmation requirement before the recommended batching strategy. Every sentence carries information; nothing is padded.

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 values need no explanation, but this destructive, confirmed mutation leaves key gaps: how confirm_token is obtained (presumably from the preview sibling), what the override parameter does, and what happens on partial failure within a range. Adequate but not complete for a write operation of this weight.

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% across five parameters, so the description must carry meaning. It implies the semantics of from_date/to_date (narrow windows around a single attempt's finishedAt) but never mentions test_id, coins_per_question_override, or how the confirm_token confirmation flow works, leaving two parameters entirely undefined.

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?

States a specific verb and resource: credits pending edubits in edubank for a test within a date range, and marks it as admin-only. An agent knows what the call does, though the existence of a preview counterpart is only hinted at by 'Pide confirmación' rather than named.

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?

Gives concrete operational guidance: use single-attempt ranges of [finishedAt - 1s, finishedAt + 1s] processed chronologically so the per-student cap is respected, and notes that already-credited items are skipped. It does not say when to call preview first or when not to use this tool at all, so it stops short of full alternative routing.

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