Skip to main content
Glama
Sign In

MolTrust MCP Server

by io.github.MoltyCel
OverviewDiscussionsAdmin

mt_salesguard_register

Register a brand with MT Salesguard.

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)

Input Schema

NameRequiredDescriptionDefault
nameYesBrand name (e.g. "Nike", "Adidas")
domainYesBrand domain (e.g. "nike.com")
contact_emailNoContact email for the brand (optional)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / contact_email / description
      Added value: +"Contact email for the brand (optional)"
    • addedInput schema / properties / domain / description
      Added value: +"Brand domain (e.g. \"nike.com\")"
    • addedInput schema / properties / name / description
      Added value: +"Brand name (e.g. \"Nike\", \"Adidas\")"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, and idempotent=false, so the description usefully adds that the call mints a DID and an API key and that the API key authorizes later reseller and product flows. That goes beyond the annotations. It stops short of stating whether the API key is returned once and unrecoverable, or what happens on a duplicate registration.

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?

Purpose is front-loaded in the first two sentences, and the credential purpose is explained before the Args block. The Args block duplicates the schema word for word, so it is mildly redundant but does not obscure the key information.

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?

An output schema exists, so return values need not be explained, and the description covers the main side effect: a created identity plus an API key. The remaining gaps are duplicate-registration behavior and whether the API key is shown only once, which matter for a non-idempotent creation tool.

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 description coverage is 100%, so the schema already documents all three parameters, including the examples for name and domain. The Args block in the description restates the schema verbatim and adds no format, validation, or domain-ownership semantics. That makes it baseline-3 under the high-coverage rule.

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: "Register a brand with MT Salesguard" and "Creates a new brand identity with a DID and API key." That is clearly distinguishable from sibling read/verify tools like mt_salesguard_verify, but the description never names those siblings or explains the relationship between register, reseller, and verify.

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?

Usage is implied: you call this first to obtain the credential needed for "product registration and reseller authorization requests," which hints that mt_salesguard_reseller/verify come after. However, there is no explicit when-to-use/when-not-to-use statement and no mention of what happens if the brand or domain is already registered.

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

All MolTrust MCP Server toolsInspect
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