Skip to main content
Glama

list_pos

Retrieves purchase orders for a specified vendor, enabling accounts-payable clerks to review and match invoices against existing orders.

Instructions

Purchase orders for a vendor.

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": {
      "vendor_id": "<vendor_id>"
    },
    "name": "list_pos"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does almost none of it. It does not state whether results include closed/paid orders, whether pagination or limits apply, or whether the call is read-only, though 'list' weakly implies a safe read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single short fragment with no wasted words, but the brevity stems from under-specification rather than tight writing. There is no front-loaded statement of what the tool actually returns or does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter listing tool this could be acceptable, but with no output schema and no annotations the description leaves the return shape, filtering behavior, and result volume entirely undocumented. An agent cannot predict what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required parameter, and the phrase 'for a vendor' only restates what vendor_id already conveys. It adds no format or constraint information, such as whether the value is an internal ID or a name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Purchase orders for a vendor' identifies the resource and the scoping filter, but supplies no verb, so an agent must infer from the name list_pos that this is a listing operation. It also does not distinguish this from the sibling get_po, which plausibly retrieves a single order.

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 when-to-use guidance, no mention of when not to use it, and no pointer to alternatives such as get_po or link_po. The only implied context is that a vendor must be known first, which is left entirely to inference.

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