Skip to main content
Glama

Remove a space deadline

remove_space_deadline
DestructiveIdempotent

Removes a single deadline from a space while leaving its files and facts unchanged; use it to clear outdated or incorrect deadlines without affecting stored content.

Instructions

Remove one deadline from a space (its files and facts are not touched).

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": "remove_space_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYes
deadline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description earns credit for adding the blast-radius constraint — only the deadline is removed and files/facts are untouched — which is exactly the context an agent needs before a destructive call. It leaves out whether deletion is reversible or how a missing deadline_id is handled, keeping it below 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?

A single sentence with the action front-loaded and the scope-limiting parenthetical placed immediately after it. Nothing is redundant and nothing needs trimming.

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?

For a simple two-parameter destructive delete with annotations covering safety and no output schema, the description is close to sufficient — it explains impact precisely. The decisive gap is that neither required identifier is described anywhere, which for a mutation tool where a wrong ID means deleting the wrong thing is material.

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% for two required parameters, so the description must carry the burden and does not: space_id and deadline_id are only obliquely implied by 'from a space' and 'one deadline'. No format, source, or ID-origin guidance is given, leaving both identifiers undocumented in the entire definition.

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+resource pair ('Remove one deadline from a space') with a clear cardinality scope ('one deadline'), which distinguishes it from add_space_deadline and update_space_deadline. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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?

Usage is implied: call this to delete an existing deadline. There is no explicit when-to-use paragraph, no exclusion (e.g., 'use update_space_deadline to change a deadline instead of removing it'), and no prerequisite such as the deadline having to exist first.

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