Skip to main content
Glama

reservations

Read-onlyIdempotent

List current file claims across all three agents, showing who reserved what, why, and until when so you can coordinate edits and avoid conflicts.

Instructions

Current file reservations of all three agents: who, what, why, until when.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reservations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
activeYes
statusYes
late_noteNo
late_repliesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.8.7
    • addedOutput schema / $defs
      Added value: +{
      +  "Attachment": {
      +    "properties": {
      +      "mime": {
      +        "title": "Mime",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "path": {
      +        "title": "Path",
      +        "type": "string"
      +      },
      +      "size": {
      +        "title": "Size",
      +        "type": "integer"
      +      }
      +    },
      +    "title": "Attachment",
      +    "type": "object"
      +  },
      +  "RenderedMessage": {
      +    "properties": {
      +      "attachments": {
      +        "items": {
      +          "$ref": "#/$defs/Attachment"
      +        },
      +        "title": "Attachments",
      +        "type": "array"
      +      },
      +      "cancelled": {
      +        "title": "Cancelled",
      +        "type": "string"
      +      },
      +      "created": {
      +        "title": "Created",
      +        "type": "string"
      +      },
      +      "due": {
      +        "title": "Due",
      +        "type": "string"
      +      },
      +      "from": {
      +        "title": "From",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "info": {
      +        "title": "Info",
      +        "type": "boolean"
      +      },
      +      "quality": {
      +        "title": "Quality",
      +        "type": "string"
      +      },
      +      "reply_to": {
      +        "title": "Reply To",
      +        "type": "string"
      +      },
      +      "state": {
      +        "title": "State",
      +        "type": "string"
      +      },
      +      "text": {
      +        "title": "Text",
      +        "type": "string"
      +      },
      +      "to": {
      +        "title": "To",
      +        "type": "string"
      +      },
      +      "topic": {
      +        "title": "Topic",
      +        "type": "string"
      +      },
      +      "vote": {
      +        "title": "Vote",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "from",
      +      "to",
      +      "topic",
      +      "created",
      +      "text"
      +    ],
      +    "title": "RenderedMessage",
      +    "type": "object"
      +  },
      +  "Reservation": {
      +    "properties": {
      +      "agent": {
      +        "title": "Agent",
      +        "type": "string"
      +      },
      +      "exclusive": {
      +        "title": "Exclusive",
      +        "type": "boolean"
      +      },
      +      "expires": {
      +        "title": "Expires",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "paths": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "title": "Paths",
      +        "type": "array"
      +      },
      +      "reason": {
      +        "title": "Reason",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "agent",
      +      "paths"
      +    ],
      +    "title": "Reservation",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / active
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/Reservation"
      +  },
      +  "title": "Active",
      +  "type": "array"
      +}
    • addedOutput schema / properties / late_note
      Added value: +{
      +  "title": "Late Note",
      +  "type": "string"
      +}
    • addedOutput schema / properties / late_replies
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/RenderedMessage"
      +  },
      +  "title": "Late Replies",
      +  "type": "array"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "title": "Result",
      -  "type": "string"
      -}
    • addedOutput schema / properties / status
      Added value: +{
      +  "const": "success",
      +  "title": "Status",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "status",
      +  "active"
      +]
    • changedOutput schema / title
      Previous value: -"reservationsOutput"New value: +"ReservationsOut"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine scope information: it returns reservations for ALL three agents rather than being scoped to the caller, which is behavior an agent could not infer from the annotations.

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 front-loaded sentence with no filler; every clause (scope, plus the four returned dimensions) earns its place.

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?

With zero params, an existing output schema, and full annotation coverage, the description only needs to establish scope and purpose, which it does. The remaining gap is routing: nothing tells the agent when this beats the adjacent reservation-listing siblings.

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?

The tool takes zero parameters, which is the baseline-4 case; there are no argument semantics to explain. The clause 'of all three agents' usefully signals that no filtering parameter is expected or needed.

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?

Names the resource precisely (current file reservations) and enumerates the returned dimensions (who, what, why, until when), so an agent knows this is a state-inspection read. It does not explicitly contrast itself with siblings like file_reservation_paths or reserve/release, so the verb and boundary are inferred 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?

The phrase 'Current file reservations' implies you call this to inspect live reservation state, but there is no explicit when-to-use instruction and no mention of the alternative reservation tools (file_reservation_paths, release_file_reservations) or when to prefer them.

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