Skip to content

Commit bac4042

Browse files
authored
Fix tabs
1 parent 64dfa91 commit bac4042

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/functions-bindings-mcp-trigger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ See the [Example section](#example) for complete examples.
153153

154154
The MCP protocol enables an MCP server to make known to clients other properties of a tool endpoint. In C#, you can define properties of your tools as either input parameters using the `McpToolProperty` attribute to your trigger function code or by using the `FunctionsApplicationBuilder` when the app starts.
155155

156-
### [`McpToolPropertyAttribute`](#tab\attribute)
156+
### [McpToolPropertyAttribute](#tab\attribute)
157157

158158
You can define one or more tool properties by applying the `McpToolProperty` attribute to input binding-style parameters in your function.
159159

@@ -167,7 +167,7 @@ The `McpToolPropertyAttribute` type supports these properties:
167167

168168
You can see these attributes used in the `SaveSnippet` tool in the [Examples](#example).
169169

170-
### [`FunctionsApplicationBuilder`](#tab\builder)
170+
### [FunctionsApplicationBuilder](#tab\builder)
171171

172172
You can define tool properties in your entry point (program.cs) file by using the `McpToolBuilder` returned by the `ConfigureMcpTool` method on `FunctionsApplicationBuilder`. This examples calls the `WithProperty` method on the builder for the `GetSnippet` tool to set the properties of the tool:
173173

0 commit comments

Comments
 (0)