Skip to main content
Glama

Set Test Published

set_test_published
DestructiveIdempotent

Publishes or unpublishes a test to control whether students can see it. Use only when explicitly requested.

Instructions

Publica (visible para los alumnos) o despublica un test. Úsalo SOLO si el usuario lo pide explícitamente.

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>",
      "published": "<published>"
    },
    "name": "set_test_published"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes
publishedYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation profile is known. The description adds the meaningful consequence that publishing makes the test visible to students. It does not say what unpublishing does to in-progress attempts or existing results, which is the key risk for a destructive flag.

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, effect stated first and the guardrail second; nothing is padded. It is arguably too terse given the parameter documentation gap, but there is no wasted wording.

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 and annotations cover safety and idempotency, so return values need not be described. Still, for a destructive toggle with zero schema descriptions, the definition omits parameter meaning and the impact of unpublishing on existing student data.

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%, so the description must compensate for both parameters. It only implies the boolean via 'publica o despublica' and says nothing about what test_id refers to or what happens with an invalid/nonexistent id.

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 gives a specific verb pair and resource ('Publica ... o despublica un test') and clarifies the concrete effect ('visible para los alumnos'). It is clearly distinguishable from siblings like get_test or export_test, though it doesn't name an alternative.

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 states an explicit usage constraint: only call when the user explicitly asks for it. That provides a real when-to-use gate, but there are no exclusions or named alternatives for related tasks (e.g. editing test content instead of publishing).

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