phoenix-oss/llama-stack-mirror
0
0
Fork 1
mirror of https://github.com/meta-llama/llama-stack.git synced 2025-10-09 21:18:38 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

llama3_1 -> llama3

Browse source
This commit is contained in:
Ashwin Bharambe 2024-08-20 19:00:47 -07:00
parent 75bbe787b6
commit c736e5b576
4 changed files with 69 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

43
rfcs/RFC-0001-llama-stack-assets/llama-stack-spec.html
View file

@ -21,7 +21,7 @@
"info": {
"title": "[DRAFT] Llama Stack Specification",
"version": "0.0.1",
"description": "This is the specification of the llama stack that provides\n a set of endpoints and their corresponding interfaces that are tailored to\n best leverage Llama Models. The specification is still in draft and subject to change.\n Generated at 2024-08-15 17:30:18.232105"
"description": "This is the specification of the llama stack that provides\n a set of endpoints and their corresponding interfaces that are tailored to\n best leverage Llama Models. The specification is still in draft and subject to change.\n Generated at 2024-08-20 19:00:39.110138"
},
"servers": [
{
@ -2580,6 +2580,9 @@
}
]
}
},
"tool_prompt_format": {
"$ref": "#/components/schemas/ToolPromptFormat"
}
},
"additionalProperties": false,
@ -2726,6 +2729,15 @@
"on_violation_action"
]
},
"ToolPromptFormat": {
"type": "string",
"enum": [
"json",
"function_tag"
],
"title": "This Enum refers to the prompt format for calling zero shot tools",
"description": "`json` --\n Refers to the json format for calling tools.\n The json format takes the form like\n {\n \"type\": \"function\",\n \"function\" : {\n \"name\": \"function_name\",\n \"description\": \"function_description\",\n \"parameters\": {...}\n }\n }\n\n`function_tag` --\n This is an example of how you could define\n your own user defined format for making tool calls.\n The function_tag format looks like this,\n <function=function_name>(parameters)</function>\n\nThe detailed prompts for each of these formats are defined in `system_prompt.py`"
},
"AgenticSystemCreateResponse": {
"type": "object",
"properties": {
@ -4768,31 +4780,31 @@
],
"tags": [
{
"name": "MemoryBanks"
},
{
"name": "Observability"
},
{
"name": "Evaluations"
},
{
"name": "Inference"
"name": "RewardScoring"
},
{
"name": "AgenticSystem"
},
{
"name": "SyntheticDataGeneration"
},
{
"name": "Inference"
},
{
"name": "Datasets"
},
{
"name": "Observability"
},
{
"name": "PostTraining"
},
{
"name": "SyntheticDataGeneration"
"name": "MemoryBanks"
},
{
"name": "RewardScoring"
"name": "Evaluations"
},
{
"name": "Attachment",
@ -4938,6 +4950,10 @@
"name": "ShieldDefinition",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/ShieldDefinition\" />"
},
{
"name": "ToolPromptFormat",
"description": "This Enum refers to the prompt format for calling zero shot tools\n\n`json` --\n Refers to the json format for calling tools.\n The json format takes the form like\n {\n \"type\": \"function\",\n \"function\" : {\n \"name\": \"function_name\",\n \"description\": \"function_description\",\n \"parameters\": {...}\n }\n }\n\n`function_tag` --\n This is an example of how you could define\n your own user defined format for making tool calls.\n The function_tag format looks like this,\n <function=function_name>(parameters)</function>\n\nThe detailed prompts for each of these formats are defined in `system_prompt.py`\n\n<SchemaDefinition schemaRef=\"#/components/schemas/ToolPromptFormat\" />"
},
{
"name": "AgenticSystemCreateResponse",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/AgenticSystemCreateResponse\" />"
@ -5302,6 +5318,7 @@
"ToolDefinition",
"ToolExecutionStep",
"ToolParamDefinition",
"ToolPromptFormat",
"ToolResponse",
"ToolResponseMessage",
"TrainEvalDataset",