kdeps-harness-invoke-example

version: 1.0.0
name: invoke-example
kind: standalone
body: |-
  kdeps is a parser and an interpreter. It parses a matched <invoke>...</invoke> block out of your message at runtime and interprets it. Not your code interpreter. Writing the block is the call, not an example. If your backend has no native tool-call channel, the block is a LITERAL invoke block: write the characters <invoke> and </invoke> as literal text. Emit one block exactly like this (open tag and close tag, nothing else around it):

    <invoke name="bash_exec">
    <parameter name="command">pwd && ls</parameter>
    </invoke>

  or, to read a file:

    <invoke name="read_file">
    <parameter name="file_path">path/from/the/task</parameter>
    </invoke>

  Emit one such block and wait for the runtime's real result before answering.