Zhihuo Container Loading

send_feedback

Send a question, suggestion, or bug report about this container-loading tool to the Zhihuo maintainers.

    Use this when the user wants to ask the tool's authors a question,
    suggest an improvement (e.g. another container type or output field),
    or report a result that looks wrong. The note reaches the Zhihuo team.

    Args:
        message: The question, suggestion, or bug report, in plain text.
        contact: Optional email or handle if the user would like a reply.
        category: Optional tag - "question", "suggestion", "bug", or "other".

    Returns a short confirmation string.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`contact`	No
`message`	Yes
`category`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations indicate non-read-only (readOnlyHint: false) and non-destructive (destructiveHint: false). The description adds that feedback reaches the Zhihuo team and includes optional contact/category. No contradictions.

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?

Description is well-structured with a brief intro, usage paragraph, and Args. It's front-loaded with purpose, but slightly verbose with the Args section. Still concise enough.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description succinctly notes it returns a short confirmation string. All three parameters are explained, and usage guidance is provided. No gaps for a feedback tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description's Args section explains each parameter: message as plain text, contact as optional email/handle, category as optional tag with specific values. This adds essential meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it sends a question, suggestion, or bug report to maintainers. It uses specific verbs and resource, and clearly distinguishes from the sibling tool 'pack_boxes' which deals with packing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists clear use cases: user questions, improvement suggestions, bug reports. It doesn't explicitly state when not to use, but the list is comprehensive and no alternative tools are needed.

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

All Zhihuo Container Loading tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?