Skip to main content
Glama

mt_salesguard_reseller

Read-only

Verify whether a reseller DID is authorized by a brand to sell specific products, returning authorization status, brand details, authorized SKUs, and expiry.

Instructions

Verify reseller authorization via MT Salesguard.

Checks whether a reseller DID has been authorized by a brand to sell specific products. Returns authorization status, brand info, authorized SKUs, and expiry.

Args: reseller_did: Reseller DID (e.g. "did:web:sneakerstore.com")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reseller_did": "<reseller_did>"
    },
    "name": "mt_salesguard_reseller"
  }
}

Input Schema

NameRequiredDescriptionDefault
reseller_didYesReseller DID (e.g. "did:web:sneakerstore.com")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / reseller_did / description
      Added value: +"Reseller DID (e.g. \"did:web:sneakerstore.com\")"
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about what is returned (status, brand info, authorized SKUs, expiry), but that overlaps with the existing output schema and it says nothing about failure modes, e.g. an unregistered DID or an unauthorized reseller.

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 sentence and the summary of returned fields follows logically. The Args block restates the schema description verbatim, which is a small redundancy but not damaging.

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?

For a one-parameter read-only verification tool with an output schema and readOnlyHint annotation, the description covers intent and result shape adequately. Only negative-path behavior is left undocumented.

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 coverage is 100% for the single parameter, and the description merely repeats the same DID example verbatim from the schema. No additional meaning (format constraints, resolution behavior for did:web) is added, so the baseline of 3 applies.

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: verifying whether a reseller DID has been authorized by a brand to sell specific products. The 'reseller' scope in the name plus the description distinguishes it reasonably from the sibling register/verify tools, though it never explicitly contrasts with them.

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?

The use case is implied clearly enough (checking reseller authorization before relying on a reseller), but there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as mt_salesguard_verify or mt_salesguard_register. The agent must infer routing.

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