Built-in MCP Tools
Hantera provides read-only built-in tools on its MCP server. Their names use the reserved system_ prefix; app and tenant tools are exposed separately through MCP ingresses.
This page describes the built-ins available in the current platform. Call tools/list on your connected server for the tools your session can use and their published schemas; availability can differ by server version and permissions.
Permissions
Each tool requires mcp/tools/system/<tool-name>:call. For example, system_graph_query requires mcp/tools/system/system_graph_query:call. The broader mcp/tools/system:call grants access to all built-ins, and mcp/tools:call covers both built-in and ingress tools. Tools without an applicable grant are hidden from discovery and calls appear as unknown tools.
Some tools also enforce the caller's underlying Graph, registry, trace, or statistics permissions, as noted below. By contrast, the fixed reporting tools and the inventory snapshot returned by system_open_sku are governed by their own tool gates; do not assume Graph field or node restrictions apply to these data products. Portal views use the separately signed-in Portal user's permissions.
Graph and tenant configuration
| Tool | Purpose | Additional permission |
|---|---|---|
system_graph_query | Run read-only Graph queries with filters, selected fields, navigations, and counts. | Applicable Graph node, edge, filter, and field permissions |
system_get_registry_value | Read one registry entry by exact key. | registry:read or an applicable registry/<path>:read grant |
system_list_registry_keys | Browse registry keys by prefix, with limit and after pagination. | registry:read or an applicable registry/<path>:read grant |
Registry tools never reveal secret entries. Signals are excluded and have their own tool. Graph queries are bounded; consult tools/list for the input schema and Graph for the query model.
Monitoring
| Tool | Purpose | Additional permission |
|---|---|---|
system_list_signals | List active platform signals, filterable by severity and path. | registry/signals:read or registry:read |
system_list_traces | List trace summaries with time, status, and resource filters and cursor pagination. | traces:read |
system_get_trace | Retrieve a trace's span tree by traceId, without captured payloads. | traces:read |
system_get_statistics | Retrieve ingress, egress, host, job, and queue statistics for a time range. | ingresses:statistics for ingresses, egresses:statistics for egresses and hosts, jobs:statistics for jobs and queues |
Statistics sections without the relevant backing permission are reported as unavailable. The time range is limited to seven days.
Portal navigation
These tools attach the reusable Portal MCP App. In hosts that support MCP Apps, the user can open the requested view and sign in to the Portal separately; Portal access and actions use that user's own session permissions.
| Tool | Purpose | Main input |
|---|---|---|
system_search_orders | Open the order list with a search phrase. | phrase |
system_open_order | Open a specific order. | orderNumber |
system_search_inventory | Open the inventory list with a search phrase. | phrase |
system_open_sku | Open a SKU and return its current per-inventory stock snapshot. | skuNumber |
system_open_portal | Open the Portal's default start view. | None |
Except for the system_open_sku snapshot, these tools provide navigation rather than returning the Portal view's business data. The snapshot is returned over MCP under the tool's own permission.
Sales and operations reporting
These tools return fixed, read-only data products. Their tool permissions govern the data returned, rather than individual Graph permissions. Time-based reports generally take an inclusive periodFrom, an exclusive periodTo, and an IANA zone; system_product_sales uses a period and requires either currency or normalizedCurrency for ranking. See each tool's schema for supported filters and arguments.
| Tool | Purpose |
|---|---|
system_product_sales | Rank product or other order-line groups by sales for a confirmed-order cohort. |
system_sales_performance | Report order counts and confirmed-order revenue over time. |
system_sales_item_performance | Report merchandise, discounts, and current returns for an order cohort. |
system_return_activity | Report returns created in a period, including returns against older orders. |
system_fulfillment_performance | Report fulfillment workload, states, completion duration, and shipping value. |
system_payment_activity | Report payment journal activity and authorizations over time. |
system_invoice_performance | Report invoice values, captures, outstanding amounts, and cancellations. |
system_list_product_sales_dimensions | List available groupBy dimensions for product sales. |
system_list_channels | List configured sales channel keys and labels for report filters. |
Related
- MCP API reference — endpoint, discovery, and invocation.
- Model Context Protocol — connection and authorization.
- MCP ingresses — expose app or tenant components as tools.