contract-cli-mdm-vendor

contract-cli MDM Vendor

CRITICAL — before starting, MUST first read ../contract-cli-shared/SKILL.md。

Applicable commands

Known vendor ID: directly use mdm vendor get
Only know the name or want a candidate list: use mdm vendor list
If the user wants to confirm field definitions before creating: switch to ../contract-cli-mdm-fields/SKILL.md
If the user wants to create or update a vendor: the current structured command does not implement this; clearly state it is not yet covered; do not fall back to api call

mdm vendor list supports --name、--page-size、--page-token
mdm vendor list --as user goes through /open-apis/contract/v1/mcp/vendors
mdm vendor list --as bot goes through /open-apis/mdm/v1/vendors
mdm vendor get --as user goes through /open-apis/contract/v1/mcp/vendors/{vendor_id}
mdm vendor get --as bot goes through /open-apis/mdm/v1/vendors/{vendor_id}
Does not expose --operator
--user-id-type / --user-id is still passed through per shared rules, without local validation
The recommended reading order is:
- First read references/vendor-query-guide.md to select the query scenario
- Then read references/vendor-query-parameters.md to look up request parameter mappings
- Finally read references/commands.md to copy command examples

When only the name is known, first mdm vendor list to get candidates, then mdm vendor get to look up details
Before creating a contract, if you just need to choose the counterparty entity, prioritize remembering the vendor id
When you want to confirm the write interface field definitions, switch to mdm fields list

Do not treat mdm vendor list/get as a field configuration query
Do not treat the unimplemented mdm vendor create/update as an existing structured command