Return the public ACE Commerce Trust Network manifest: participants, protocol interoperability state, extension points, and the rule that network membership never grants truth authority.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It says 'Return', implying a read-only operation, but does not explicitly state that it is safe or non-mutating. It also does not mention potential size, latency, or error behavior. The reference to a rule about truth authority is content, not tool behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core action and resource, then covers the key components. There is no verbosity or redundancy—every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description effectively lists what the manifest contains, which covers the primary information an agent needs to understand the result. It could briefly note when this tool is intended to be used (e.g., for network overview), but the current detail is adequate for a simple fetch operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the schema coverage is trivially 100%. The baseline for 0 params is 4, and the description correctly avoids discussing parameters that don't exist, adding no unnecessary semantic burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Return the public ACE Commerce Trust Network manifest' and enumerates its contents (participants, protocol interoperability state, extension points, and the rule about truth authority). This specific verb+resource combination differentiates it from the sibling 'commerce_trust_graph', which implies a graph-based query rather than a manifest fetch.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'commerce_trust_graph' or 'commerce_capabilities'. The description only explains what it returns, leaving the agent to infer the appropriate context or prerequisites without any explicit when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct workflow stages (discovery, identity, claims, decision, referral), and the detailed descriptions help separate them. However, ace_check and commerce_preflight both expose ACE Verdict decisions, and verify_global_offer is an explicitly legacy alternative to commerce_preflight, so an agent can still misselect among the verification/decision tools.
All names are readable snake_case, and action tools use a verb_object pattern while query/metadata tools use noun phrases. The split is not chaotic, but it is inconsistent (e.g., product_discovery vs resolve_product_identity), and the commerce_/commercial_ prefix variation adds a minor wrinkle.
Fifteen tools is at the upper end of a well-scoped service and is reasonable for a broad commerce intelligence domain. The count feels slightly heavy because there are several descriptive/policy tools and at least one legacy overlap (verify_global_offer) that could be consolidated.
The set covers the core pre-purchase workflow: discovery, identity resolution, claim compilation, verification, recalls, merchant readiness, trust, referrals, and routing. Minor gaps exist, such as no explicit claim-management or decision-status retrieval separate from the decision products, but these do not create dead ends.