Skip to main content
Glama

uplus_audit_experiment

Audit a submitted experiment report for completeness: detects empty reports, leftover placeholders and mismatched experiment files, and flags any report that could not be downloaded.

Instructions

Read-only completeness audit for a submitted experiment.

Pulls the submitted report back when the page exposes a download link and checks it for an empty body, leftover placeholders and a report written for a different experiment. When the file cannot be downloaded, the audit says so and only checks the page record — it never reports an unchecked report as clean. It withdraws and submits nothing.

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": {
      "course_id": "<course_id>",
      "exp_id": "<exp_id>",
      "stu_exp_id": "<stu_exp_id>"
    },
    "name": "uplus_audit_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
exp_idYes
downloadNo
course_idYes
stu_exp_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.3

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the download-dependent behavior, the three specific checks (empty body, leftover placeholders, wrong-experiment report), and the degraded path when download fails, including the explicit guarantee that an unchecked report is never reported as clean. It also confirms the tool is non-mutating. It omits any note on permissions or returned result shape, keeping it from 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.

Conciseness5/5

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

The description is front-loaded with the single-sentence purpose, then layers in mechanics, failure behavior, and the safety guarantee in short, earned sentences. No sentence is redundant or restates the tool name. The closing 'It withdraws and submits nothing' is a compact, high-value constraint.

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?

Given a four-parameter tool with zero annotation coverage and no output schema, the description explains the audit logic and its failure mode well but leaves the parameters entirely undocumented and gives no sense of what the returned audit actually contains. It is adequate for deciding whether to call it, but incomplete for calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must compensate and it does not. The `download` boolean (default true) is never mentioned, despite mapping directly onto the described download-link behavior, and course_id, exp_id, and stu_exp_id are left entirely unexplained. An agent would have to guess what identifies the target experiment.

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 first line names a specific verb and resource: a 'read-only completeness audit for a submitted experiment,' which is distinct from sibling actions like submitting or inspecting. It is clear what the tool produces (a completeness verdict on a report). It stops short of naming which sibling to use instead, so it lands at 4 rather than 5.

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 implies the usage context (verifying a submitted report, presumably before submitting) and states a boundary ('It withdraws and submits nothing'), which is helpful. However, it never says when to choose this over uplus_inspect_experiment or uplus_generate_experiment_report, and gives no explicit prerequisites. Guidance is implied rather than stated.

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