SuperAPI AI Directory

contract-cli-mdm-legal

Office & productivity

View repository

Updated 10-15 21:41

About this skill

contract-cli MDM Legal

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

Applicable commands

  • contract-cli mdm legal list
  • contract-cli mdm legal get <legal-entity-id>

Quick decision

  • Known legal entity ID: use mdm legal get
  • Only know the name and need a candidate list: use mdm legal list
  • If the user wants to query field configuration: switch to ../contract-cli-mdm-fields/SKILL.md
  • If the user wants to create or update a legal entity: the current structured command does not implement this; do not fake it

Key rules

  • mdm legal list supports --name、--page-size、--page-token
  • mdm legal list --as user goes through /open-apis/contract/v1/mcp/legal_entities
  • mdm legal list --as bot goes through /open-apis/mdm/v1/legal_entities/list_all
  • mdm legal get --as user goes through /open-apis/contract/v1/mcp/legal_entities/{legal_entity_id}
  • mdm legal get --as bot goes through /open-apis/mdm/v1/legal_entities/{legal_entity_id}, and additionally passes through query legal_entity_id
  • does not expose --operator
  • --user-id-type / --user-id is still passed through according to shared rules, with no local validation
  • Recommended reading order is:

Implementation source

Operation suggestions

  • When only the entity name is known, first mdm legal list to get candidates, then mdm legal get to query details
  • Before creating a contract, if you only need to select our entity, prioritize remembering the legal entity id
  • When you want to confirm the field definitions of the write API, switch to mdm fields list

Do not do this

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