Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions schema-demos/schema-demo-max-tool-denials.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
description: Demonstrates the `max-tool-denials` schema field
on:
workflow_dispatch:
permissions:
contents: read
engine:
id: copilot
copilot-sdk: true
max-tool-denials: 5

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[/grill-with-docs] max-tool-denials: 5 is the schema default value — using it here makes the demo indistinguishable from omitting the field entirely.

💡 Suggestion

The JSON schema notes "default": 5 for this field. To unambiguously show the field is intentionally configured (and to match the validation test which uses 6), prefer a non-default value:

max-tool-denials: 3

This makes the demo self-documenting: a reader can immediately see the field is set to a deliberate value, not accidentally left at its default.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Demo uses the schema default value — indistinguishable from omitting the field. max-tool-denials: 5 is the schema default ("default": 5), so this demo cannot be distinguished at runtime from a workflow that omits the field entirely.

💡 Suggested fix

Change the demo value to any non-default integer so the file clearly shows the field overriding the default:

max-tool-denials: 3

The validation test (max_tool_denials_validation_test.go) deliberately uses 6 (not 5) for exactly this reason. A coverage demo whose value equals the default only proves the YAML key is parseable — it does not demonstrate the field changing engine behaviour.

timeout-minutes: 5
---

# Schema Demo: `max-tool-denials`

This workflow was auto-generated to demonstrate usage of the `max-tool-denials` field in the
gh-aw frontmatter schema. It exists solely to achieve 100% schema feature coverage.

## What `max-tool-denials` Does

Copilot SDK safeguard threshold for repeated tool denials before stopping inference.

## Task

Call `noop` -- this is a coverage-only demo workflow.

**Important**: Always call the `noop` safe-output tool.

```json
{"noop": {"message": "Coverage demo for `max-tool-denials` -- no action needed."}}
```
Loading