Skip to main content
Glama

Add a lot (Record plan)

create_lot
Destructive

Adds a lot to the signed-in Record account, the same as POST /v1/lots (https://provkeep.com/developers). Its certificate is uploaded and confirmed by a person on provkeep.com, never through this tool. Set activate to true when the lot starts shipping now.

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": {
      "peptide": "<peptide>",
      "lot_number": "<lot_number>"
    },
    "name": "create_lot"
  }
}

Input Schema

NameRequiredDescriptionDefault
peptideYesThe product's name, e.g. BPC-157.
activateNoTrue when this lot is the one shipping from now on.
lot_numberYesThe lot number exactly as it appears on the certificate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false), the description supplies real process context: the certificate is uploaded and confirmed by a human on provkeep.com and never through this tool, which prevents an agent from attempting an impossible action. It stops short of explaining retry semantics for a non-idempotent create (duplicate lots) or what happens on failure, which the destructiveHint flag makes relevant.

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?

Three short sentences, front-loaded with what the tool does, followed by the out-of-band constraint and the one conditional parameter note. The developer URL is slightly extraneous but not distracting; no sentence is filler.

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 mutation tool with no output schema, the description covers the write and its annotations but leaves the return value unspecified — an agent cannot tell whether a lot identifier comes back that would be needed to chain into record_lot_dates or list_lots. The out-of-band certificate flow is covered, but failure and duplicate-handling behavior are not.

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%, with each of the three parameters documented in the schema itself, so the baseline is 3. The description only restates the activate condition already present in the schema ('True when this lot is the one shipping from now on') and adds no format, validation, or edge-case detail for peptide or lot_number beyond what the schema says.

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 and resource ('Adds a lot') plus the target scope ('the signed-in Record account') and equates it to POST /v1/lots, so the effect is unambiguous. It does not explicitly distinguish itself from siblings such as record_lot_dates or record_order, though the names imply different resources, so it lands just below top marks.

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 only implied: the reader infers this is the entry point for registering a new lot, and the activate sentence gives a conditional for one parameter. There is no statement of prerequisites (a signed-in account is required but not framed as a precondition), no mention of what to do if the lot already exists, and no routing advice relative to record_lot_dates or list_lots.

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