Skip to main content
Glama

Read requisition list

read_requisition_list
Read-onlyIdempotent

Retrieve a user's saved requisition (reorder) lists, or pass a list ID to get that list's SKUs and quantities.

Instructions

Without list_id: the user's saved requisition (reorder) lists. With list_id: that list's SKUs and quantities.

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

Input Schema

NameRequiredDescriptionDefault
list_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safe read-only, idempotent, non-destructive profile, and the description adds valuable mode-dependent return behavior: list overview without list_id and SKU/quantity details with list_id. It does not address pagination, invalid IDs, or empty-list behavior, but it meaningfully supplements 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?

The description is two compact conditional clauses with no redundant wording. The mode distinction is front-loaded and immediately actionable.

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 read tool with one optional parameter, annotations, and no output schema, the description explains both call modes and the essential returned content. Minor operational details such as pagination or error behavior are absent, but nothing critical is missing for correct invocation.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It does: list_id is optional and changes the resource from the user's saved requisition lists to one specific list's SKUs and quantities, compensating well for the bare string schema.

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 read operation on the user's saved requisition lists and clearly distinguishes the two modes: listing requisitions versus reading one list's SKUs and quantities. It does not explicitly contrast with sibling tools, but the resource is specific enough that an agent can identify what it returns.

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 through the conditional description: omit list_id to see saved requisition lists, provide list_id to see that list's contents. There is no explicit guidance on when to choose this over related tools or on exclusions, so guidance is adequate but incomplete.

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