Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_order_lines_get

Retrieve a single Macola purchase order line by its ID. Use it to fetch line-level details such as item, quantity, and pricing for a specific PO entry.

Instructions

Get the Purchase Order Line for a particular entry by specifying its ID.

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": {
      "id": "<id>"
    },
    "name": "purchase_order_lines_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPurchase order line ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. The verb "Get" implies a non-mutating single-record read, but the description says nothing about behavior when the ID does not exist, permissions required, or what the returned line contains.

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?

One front-loaded sentence with no filler. The phrase "for a particular entry" is mildly redundant with the single-ID semantics, but nothing is wasted.

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 one-parameter read tool this is adequate but thin. With no output schema and no annotations, the description leaves the return payload and not-found behavior undocumented, which the agent would need when chaining this into a workflow.

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% and the schema already labels id as "Purchase order line ID". The description repeats that the ID identifies a single line entry but adds no format, sourcing, or validity detail beyond the 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?

States a specific verb and resource ("Get the Purchase Order Line") and the retrieval key ("by specifying its ID"). It does not distinguish itself from the sibling purchase_order_lines_find, so the agent must infer that this is the single-record lookup while find is the search variant.

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 phrase "for a particular entry by specifying its ID" signals this is for known-ID lookups. There is no explicit statement of when to prefer this over purchase_order_lines_find or what to do when the ID is unknown.

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

Deploy Server

Other Tools