Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

customer_items_get

Retrieve a customer item by its ID from Macola 10 to view customer-specific item details for lookups, order processing, or data validation.

Instructions

Get the Customer Item by 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": "customer_items_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCustomer item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: the word "Get" implies a read but it never says the operation is non-mutating, what happens when the ID is unknown (error vs empty), or whether permissions are required. No pagination, side effects, or response shape are described.

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 short sentence with zero filler and the key constraint (ID lookup) front-loaded. It is efficient, though its brevity borders on under-specification rather than tight economy.

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?

This is a low-complexity one-parameter read, and the schema covers that parameter completely, so the definition is minimally viable. Missing are any statement of read-only behavior and, since there is no output schema, at least a hint at what a Customer Item record contains.

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 single parameter is fully documented as "Customer item ID", so the schema already does the work; the description's "by ID" matches but adds no format, type, or sourcing detail beyond it.

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 ("Get the Customer Item") and the lookup key ("by ID"), so the agent knows exactly what call it makes. It does not differentiate from the sibling customer_items_find, leaving the get-vs-find distinction to be inferred from names alone.

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?

"By ID" weakly implies the caller must already hold a known identifier, but there is no explicit when-to-use guidance, no mention of when to prefer customer_items_find for lookups without an ID, and no preconditions stated.

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