Skip to main content
Glama

Record a lot's expiry and beyond-use dates (Record plan)

record_lot_dates
Destructive

Records a lot's expiry date, beyond-use date or both, the same as POST /v1/lots/{id}/dates. Appended: an earlier date stays on record. Takes the lot_id from list_lots or create_lot, and dates as YYYY-MM-DD.

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": {
      "lot_id": "<lot_id>"
    },
    "name": "record_lot_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
lot_idYesThe lot's id, from list_lots or create_lot.
sourceNoWhere the date comes from. Default operator.
expiry_dateNoYYYY-MM-DD.
beyond_use_dateNoYYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real value beyond the annotations by disclosing append semantics ('an earlier date stays on record'), which is the key behavioral fact an agent needs before calling a destructiveHint=true tool. However, it does not explain the interaction between that append behavior and destructiveHint, nor what happens to existing dates on repeat calls despite idempotentHint=false.

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?

Three short sentences, front-loaded with what the tool does and the append rule, with zero redundant wording. The API endpoint reference is compact and informative for agents that reason about underlying operations.

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 simple four-parameter mutation with annotations and no output schema, the description covers purpose, prerequisites, date format, and the append rule. The remaining gap is the 'source' parameter's meaning and any note on what a successful call returns or how invalid dates are handled.

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 coverage is 100%, so the schema already documents all four parameters, and the description only restates lot_id provenance and the YYYY-MM-DD format. The 'or both' phrasing usefully signals that both date parameters may be sent together, but the 'source' enum (operator vs certificate) is never explained in the description, leaving the most semantically ambiguous parameter to the schema alone.

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?

The description names a specific verb and resource (records a lot's expiry date, beyond-use date, or both) and pins the exact API operation it mirrors. It also distinguishes itself from data-retrieval siblings by noting that lot_id comes from list_lots or create_lot rather than being looked up here.

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 establishes the prerequisite clearly: the lot must already exist and its id comes from list_lots or create_lot. It also clarifies that supplying one or both dates in a single call is valid. There is no explicit when-not guidance or routing to a sibling for corrections/removals, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources