Skip to content

Commit 4315012

Browse files
authored
docs: Update the-agent-format.md
1 parent 2b600d3 commit 4315012

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

docs/the-agent-format.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,10 @@ Every manifest file consists of the following sections:
88
- [`version`](#the-version-field) — The version of the agent.
99
- [`description`](#the-description-field) — A description of the agent.
1010
- [`mcpServers`](#the-mcp-servers-field) — The MCP servers the agent has access to.
11-
- [`tools`](#the-tools-field) --- The tools available to the agent.
11+
- [`tools`](#the-tools-field) The tools available to the agent.
1212
- [`allowedTools`](#the-allowed-tools-field) — Tools that can be used without prompting.
1313
- [`toolsSettings`](#the-tools-settings-field) — Configuration for specific tools.
14+
- [`resources`](#the-resources-field) — Resources available to the agent.
1415

1516
### The `name` field
1617

@@ -128,6 +129,22 @@ The `toolsSettings` field provides configuration for specific tools. Each tool h
128129
}
129130
```
130131

132+
### The `resources` field
133+
134+
The `resources` field gives an agent access to local resources.
135+
136+
Resources are data and content that your agent has access to. As of today, only local file resources are supported, however the intention is to support surfacing MCP resources to agents as well.
137+
138+
```json
139+
{
140+
"resources": [
141+
"file://AmazonQ.md",
142+
"file://~/Documents/my-repo/README.md",
143+
"file:///tmp/my-application-logs.txt"
144+
}
145+
}
146+
```
147+
131148
## Complete Example
132149

133150
Here's a complete example of an agent manifest:

0 commit comments

Comments
 (0)