Skip to main content
Glama

Add deadlines to a space

add_space_deadline

Adds exam, homework, quiz, and project deadlines to a space with dates, times, covered files, and source links so learners see what is due and what to prioritize.

Instructions

Add one or more deadlines to a space (send all of a space's deadlines in one call): exams, homework, quizzes and projects, each with its date, its time if it has one, and which of the space's files (notes, readings) it covers. godspeed uses this to show the learner what is due and what to work on first. Take the deadlines, their dates and times from the space info files (a syllabus, a schedule), and never make up a date or time. Work out what a deadline covers from the space's own files first: a practice exam or review sheet, the schedule, announcements (search_space_files). Link the files they point to (file_ids), list files from before it that it doesn't cover in left_out_ids, and say in source which file it came from. Ask only when the files don't settle it. File ids come from read_space with files: true. A deadline that is refused is listed under refused with the reason; the others are still added, so send only the refused ones again.

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>",
      "deadlines": "<deadlines>"
    },
    "name": "add_space_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYes
deadlinesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, idempotent=false, openWorld=false; the description goes well beyond by disclosing partial-failure semantics ('A deadline that is refused is listed under refused with the reason; the others are still added, so send only the refused ones again'). It also imposes data-provenance constraints and the learner-visible effect of source and left_out_ids. The one uncovered behavior is that a duplicate call is not idempotent and would re-add the same deadlines.

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?

It is front-loaded with the action and batch rule before moving into sourcing, coverage derivation, and failure handling, and nearly every clause carries an operational instruction. It is a single dense run-on paragraph with some schema-adjacent restatement ('its date, its time if it has one'), so it would read better split into purpose / sourcing / error sections.

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 two-parameter but deeply nested write tool with no output schema, the description covers what an agent needs: batch expectation, provenance of dates, how to derive file coverage, the escalation boundary, and the partial-success/refused contract. It does not describe the success response (e.g., returned deadline ids) or note that re-sending already-added deadlines duplicates them.

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 reported at 0% (nested array of objects), so the description has to carry the burden, and it does: it defines the workflow meaning of file_ids (link the files a deadline points to), left_out_ids (files from before it that it does not cover), and source (which file it came from, learner-visible). space_id is never explained, though the reference to 'read_space with files: true' and 'a space's deadlines' makes its origin inferable.

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 first clause pairs a specific verb and resource ('Add one or more deadlines to a space') and immediately states the batch contract ('send all of a space's deadlines in one call'). Combined with the enumerated kinds (exams, homework, quizzes, projects), an agent can tell this apart from remove_space_deadline, update_space_deadline, and add_space_file 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit sourcing rules ('Take the deadlines ... from the space info files (a syllabus, a schedule), and never make up a date or time') and names the alternative tools to consult first ('search_space_files', 'read_space with files: true'). It also defines the escalation boundary ('Ask only when the files don't settle it') and a retry rule for refused items, which is real when-to-use guidance rather than generic context.

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