Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

purchase_orders_get

Retrieves a specific purchase order by ID, enabling you to look up its details in Macola 10.

Instructions

Get the Purchase Order 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_orders_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPurchase order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 disclosure burden, and it only implies read-only retrieval. It says nothing about behavior when the ID does not exist, whether it errors or returns empty, permission requirements, or what fields come back; for a keyed lookup those failure semantics matter to an agent.

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?

A single front-loaded sentence with no filler beyond slight redundancy in "for a particular entry by specifying its ID." Nothing needs to be removed, but nothing is especially well structured either.

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 trivial one-parameter lookup with no output schema, the description covers the essentials of what the tool does. It falls short on not-found behavior and returned content, which an agent may need when the call returns nothing.

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?

Only one parameter exists and its schema description ("Purchase order ID") is at 100% coverage, so the baseline is a 4. The description adds only marginal framing by emphasizing that the ID selects a particular entry, with no format or example 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?

Names a specific verb ("Get") and resource ("Purchase Order") and constrains it to a single record retrieved by ID. It does not explicitly differentiate itself from the sibling purchase_orders_find, but the keyed single-record framing is clear enough to pick correctly in most cases.

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?

The phrase "by specifying its ID" implies this is the ID-based single-record lookup rather than a search, which is useful implied guidance. However, it never states when to prefer this over purchase_orders_find, nor any prerequisite (valid ID, existing record).

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