Skip to main content
Glama

Update a space deadline

update_space_deadline
Idempotent

Change a study-space deadline's kind, name, date, time, covered or excluded files, source, assignment file, or completion status. Use it to correct requirements and track progress accurately.

Instructions

Change a deadline's kind, name, date, time, covered files, left-out files, source or assignment file, or tick it done (done: true) or not done (done: false). file_ids and left_out_ids each replace the whole list (a file is never in both); time: null, source: null and assignment_file_id: null remove them. Work out coverage from the space's own files as add_space_deadline says; ask the learner when the files don't settle it.

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": {
      "space_id": "<space_id>",
      "deadline_id": "<deadline_id>"
    },
    "name": "update_space_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD.
doneNo
kindNoWhat the deadline is.
nameNo
timeNo24-hour "HH:MM", or null to remove the time.
sourceNoWhere you found what it covers, e.g. the practice exam's file name. The learner sees it.
file_idsNoIds of the space files it covers.
space_idYes
deadline_idYes
left_out_idsNoIds of space files from before it that it does NOT cover (e.g. lectures after the practice exam's last topic). The learner's page stops flagging them as missing.
assignment_file_idNoFor homework and projects: the id of the space file with its problems (the assignment sheet). The learner works on its problems in godspeed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (idempotent, non-destructive, not read-only), the description discloses the critical mutation semantics: file_ids and left_out_ids each replace the entire list, a file can never be in both, and nulling time, source, or assignment_file_id removes those values. The done:true/false toggle is spelled out explicitly. This is exactly the context an agent needs before overwriting a list and cannot get from the schema or annotations.

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?

The mutable-field inventory is front-loaded, followed by the replacement/removal rules and then the coverage guidance in priority order. It is dense but every clause carries operational meaning. The single long opening sentence is slightly harder to parse than a short bulleted structure would be.

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 an 11-parameter mutation tool with no output schema, the description covers the risky semantics (list replacement, null removal, done toggle) and the coverage-derivation workflow. It does not address failure modes such as an unknown deadline_id or a file id outside the space, but the annotations already establish idempotency and non-destructiveness.

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

Parameters4/5

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

Schema coverage is 64%, and the description compensates for the gaps that matter: whole-list replacement for file_ids/left_out_ids, mutual exclusivity between them, and null-as-removal for the three nullable fields. It adds little about space_id, deadline_id, name, date, or kind, but those are either self-evident or already described in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb ('Change') and resource ('a deadline's...') and enumerates exactly which fields are mutable: kind, name, date, time, covered files, left-out files, source, assignment file, and done status. An agent can distinguish this from add_space_deadline and remove_space_deadline without opening any schema.

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 gives concrete operating guidance: derive coverage from the space's own files 'as add_space_deadline says,' and escalate to the learner when the files don't settle it. That routes the agent to a sibling for methodology and defines a fallback. It stops short of stating when not to use this tool (e.g., creation vs. deletion), leaving that to be inferred from sibling names.

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