MolTrust

mt_salesguard_register

Register brands on MT Salesguard to create DID-based identities and API keys for authenticating products and authorizing resellers.

Creates a new brand identity with a DID and API key. The API key is used to authenticate product registration and reseller authorization requests.

Args: name: Brand name (e.g. "Nike", "Adidas") domain: Brand domain (e.g. "nike.com") contact_email: Contact email for the brand (optional)

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`domain`	Yes
`contact_email`	No

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

A3.6/5.0

Behavior3/5

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

Describes creation of brand identity and API key purpose but omits idempotency, error cases, or side effects given no annotations.

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?

Well-structured with summary followed by Args section; no redundant sentences.

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

Completeness4/5

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

Adequate for simple 3-parameter tool; appropriately relies on output schema for return value documentation.

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

Parameters4/5

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

Compensates for 0% schema coverage by adding domain meaning (Brand name/domain) and concrete examples (Nike, nike.com).

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 specific action (register brand) and output (DID/API key), implicitly distinguishes from sibling verify/reseller tools.

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?

Implies usage context via API key purpose explanation but lacks explicit when/when-not guidance or alternative comparisons.

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MoltyCel/mol-trust'

If you have feedback or need assistance with the MCP directory API, please join our Discord server