Skip to main content
Glama

Load Business Policies

hgr_load_business_policies
Read-onlyIdempotent

Loads marketplace business policies for one visible store. 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": {
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_load_business_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is carried by structured data. The description adds only a terse note about the HGR API header and 'ChannelOAuthId resolved internally', which is thin and arguably confuses rather than clarifies how identification works.

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?

Two short sentences, front-loaded with the purpose. The second sentence is dense and slightly ambiguous but not padded.

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 and the single parameter is fully documented in the schema, so the description's remaining job is to route and disambiguate. It leaves the refresh-vs-load distinction unexplained and the 'resolved internally' clause unresolved against the required parameter.

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 100% and the parameter description already points to hgr_list_channels for obtaining the value. The description's phrase 'ChannelOAuthId resolved internally' does not add usable meaning and sits slightly at odds with the schema's required channelOAuthId, but it does not override 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 ('Loads marketplace business policies') plus a scope constraint ('one visible store'). It does not, however, distinguish itself from the sibling hgr_refresh_business_policies, which an agent could easily confuse with it.

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 'one visible store' scoping and the reference to hgr_list_channels imply how to obtain the identifier, but there is no explicit when-to-use guidance and no statement of when to prefer it over hgr_refresh_business_policies.

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