YQCloud Custom Function Calling Format Specification

This skill describes a set of custom function calling formats for ticket operations in ITSM (IT Service Management) scenarios.

Format Structure Description

Each function definition contains two layers of structure:

Outer layer: Standard function description (name, description, parameters)
Inner
```
function
```
field: Execution configuration (type, url, headers, etc.)

Function Type (function.type)

Type	Description
`manual`	Manual processing, the logic is implemented by the frontend/system itself, no HTTP request is initiated
`call_url`	Automatically initiate an HTTP request to the specified URL

Common Fields

```
stopAfterFunctionCall
```
: Whether to stop the AI from continuing to generate after calling the function (true = stop, false = continue)
```
intl
```
: Internationalization configuration, including
```
zh_CN
```
and
```
en_US
```
```
requestParser
```
: JavaScript code string,
```
data
```
is the JSON string of AI function call parameters (needs to be parsed with
```
JSON.parse(data)
```
)
```
responseParser
```
: JavaScript code string,
```
data
```
is the response body object,
```
_
```
(lodash) can be used

Variable Placeholders

```
${STATIC#yqcloud_url}
```
: YQCloud service base address
```
${tenantId}
```
: Current tenant ID
```
${yqAccessToken}
```
: Current user access token

Function List

1. createTicket — Create Ticket

Type:
```
manual
```
(handled by the frontend itself, no HTTP request is sent)
stopAfterFunctionCall:
```
true
```
Parameters:
```
additionalProperties: true
```
, accepts any fields
Calling timing: Called after obtaining the form Schema and collecting all fields from the user

2. getCreateTicketParamJsonSchema — Get Ticket Parameter Schema

Type:
```
call_url
```
, GET request

URL:

${STATIC#yqcloud_url}/ai/v1/${tenantId}/itsmScene/getServiceItemSchema

stopAfterFunctionCall:
```
false
```
Required parameter:
```
id
```
(string, service item ID)
Calling timing: Called immediately after the service item is confirmed, collect fields from the user one by one according to the returned Schema

3. getAllServiceItem — Get All Service Items

Type:
```
call_url
```
, GET request

URL:

${STATIC#yqcloud_url}/itsm/v1/${tenantId}/service_items/catalog/page/all?serviceCatalogFlag=true&page=0&size=9999

Parameters: No required parameters

responseParser: Filter

type === 'SERVICE' || type === 'RECORD'

, only retain

id

name

shortDescription

description

, return

{ allServiceItemList: [...] }

Calling timing: First step call after the user puts forward any ticket-related requirements

4. requestUserSelectServiceItem — Request User to Select Service Item

Type:
```
call_url
```
, POST request, URL:
```
/transparent
```
stopAfterFunctionCall:
```
true
```
Required parameter:
```
serviceItemList
```
(array, max 1 most likely matching service item is allowed to be passed)

responseParser:

return data?.serviceItemList ? data : {result: 'no data'}

Calling timing: Called when AI cannot determine the specific service item

Typical Calling Process

User submits ticket request
       ↓
Call getAllServiceItem
       ↓
AI analyzes and matches service items
       ├─ Match confirmed → getCreateTicketParamJsonSchema → Collect fields → createTicket
       └─ Match unconfirmed → requestUserSelectServiceItem → Re-enter the process after user selection

Notes

```
getAllServiceItem
```
actually has no required parameters, you can call it directly
The
```
serviceItemList
```
parameter of
```
requestUserSelectServiceItem
```
can pass at most 1 service item
```
createTicket
```
is of
```
manual
```
type, the actual creation logic is implemented by the frontend
After calling a function with
```
stopAfterFunctionCall: true
```
, the AI will not continue to output

yqcloud-function-calling

NPX Install

Tags

SKILL.md Content (Chinese)