Skip to main content
Glama

Post Sales Loadaddressesfromorderline

hgr_post_sales_loadaddressesfromorderline
Read-onlyIdempotent

Dedicated HGRApi tool for POST api/Sales/LoadAddressesFromOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST load addresses from order line operation in sales/order operations. Use when: Use it when a client needs to run the load addresses from order line operation for sales/order operations. Input: [FromBody] rq: LoadAddressFromOrderLineRequest. Main fields: OrderLineId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the load addresses from order line operation. Search terms: sales loadaddressesfromorderline. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

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": {
      "body": "<body>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_post_sales_loadaddressesfromorderline"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/Sales/LoadAddressesFromOrderLine request body.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description is not the sole source of safety information, but what it adds is hedged boilerplate: "Returns the result or applies the effect of the load addresses from order line operation" is ambiguous about whether state changes. It also contradicts the schema by stating "Header channel / ChannelOAuthId resolved internally" while channelOAuthId is a required caller-supplied parameter. No useful behavioral context (side effects, payload constraints, failure modes) is disclosed.

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

Conciseness2/5

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

Sentences are padded with boilerplate that adds no selection value: "This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller" and "Search terms: sales loadaddressesfromorderline". The actionable content (body payload, OrderLineId) is buried mid-paragraph rather than front-loaded.

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?

An output schema exists, so return values need not be explained, and the fixed-endpoint framing helps. Yet for a POST whose body is untyped in the schema, listing a single field and hedging on the effect leaves an agent without enough to build a correct request or know what the operation achieves.

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 coverage is nominally 100%, so the baseline is 3, and the description does contribute something by naming OrderLineId as the main body field. That contribution is limited: the body property in the schema is opaque (no type or nested properties), so an agent still cannot infer the full request payload from the description, which only lists one field.

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 description names a specific verb+resource (POST LoadAddressesFromOrderLine in sales/order operations) and pins it to a fixed endpoint, so it is not a generic caller. However, "load addresses from order line" is never explained in plain terms – an agent cannot tell whether it fetches stored addresses, computes shipping addresses, or mutates an order line. It also does not distinguish itself from close siblings such as hgr_load_order_addresses, hgr_load_shipping_options or hgr_set_shipping_address.

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?

The guidance is circular: "Use it when a client needs to run the load addresses from order line operation for sales/order operations" restates the name rather than describing a scenario. No exclusions, prerequisites, or alternatives among the many load_*/sales siblings are mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources