Skip to main content
Glama

Your lots and certificates (Record plan)

list_lots
Read-onlyIdempotent

Lists the signed-in Record account's lots: product, lot number, status, whether a person has confirmed its certificate and from which manufacturer, its expiry and beyond-use dates, how many orders it shipped on, and its public verify link. Does not count as a lookup.

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

Input Schema

NameRequiredDescriptionDefault
productNoOptional. Only this product's lots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, closed-world, idempotent, non-destructive operation. The description adds useful behavioral context by listing the returned data points and noting that the call does not count as a lookup. It does not describe pagination or result limits, but the added return-field detail is meaningful beyond 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is compact and front-loads the primary action. The long enumeration of returned fields earns its place because no output schema exists. The final sentence is short but somewhat ambiguous, slightly reducing clarity.

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 list tool with one optional filter and no output schema, the description is largely complete. It explains what is returned and the account scope, though it omits pagination, sorting, and default ordering behavior. Those gaps are minor but prevent a 5.

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 description coverage is 100% for the single optional product parameter, so the schema already explains its meaning. The description does not add further semantics about filtering or default behavior when no product is supplied. A baseline score of 3 is appropriate because the schema carries the parameter documentation.

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 states a specific verb and resource: it lists the signed-in account's lots. It also enumerates the returned fields, giving a clear sense of scope. It does not explicitly distinguish this tool from siblings such as list_products or record_lot_dates, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Does not count as a lookup' hints at metering behavior but does not tell an agent when to choose list_lots over sibling listing tools.

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