Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Publicar o pasar a borrador

set_published

Publish or unpublish a course, module, or lesson by setting its published state; confirm with the user before publishing.

Instructions

[Equipo del aula] Publica o pasa a borrador un curso, módulo o lección que puedes editar. Confirma con la persona antes de publicar.

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": {
      "classroom_id": "<classroom_id>",
      "kind": "<kind>",
      "item_id": "<item_id>",
      "published": "<published>"
    },
    "name": "set_published"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesQué se publica
item_idYesElemento
publishedYestrue para publicar, false para borrador
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's added value is the edit-permission prerequisite and the human-confirmation requirement before publishing — genuine behavior beyond the structured fields. It still does not say what a student sees after publishing or whether unpublishing affects submitted work.

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?

Two short sentences with the audience tag, the action, the editability constraint, and the confirmation rule front-loaded ahead of any call. No wasted wording.

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 4-required-parameter mutation with a fully documented schema and no output schema, the description supplies the two things the schema cannot: the permission prerequisite and the confirm-before-publish rule. Side-effect disclosure (notifications to students, effect of unpublishing) is the remaining gap.

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 100%, including an explicit 'true para publicar, false para borrador' on the boolean and a described enum, so the baseline is 3. The description adds little parameter meaning and its 'lección' label does not match the enum value 'session', which could nudge an agent toward an invalid value.

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 pair ('Publica o pasa a borrador') and the item scope ('curso, módulo o lección'), so the agent knows this is a reversible publish-state toggle rather than a create/update tool. It is not explicitly contrasted with siblings like update_course or update_lesson, and it names 'lección' where the schema enum says 'session', leaving a small naming gap.

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?

'que puedes editar' communicates a precondition (the item must be editable by the caller), and 'Confirma con la persona antes de publicar' gives a concrete workflow rule before the irreversible-feeling publish action. It does not state when to prefer this over update_course/update_module, but the usage context is clear enough to act on.

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

Deploy Server

Other Tools