Get Args Schema For Tool
Description
Returns the JSON Schema that validates the args property of a mutation tool, together with the AttackForge richtext format spec whenever that schema contains rich-text fields.
Whether you need this call depends on the tool. For the dynamic-shape tools the shape of args is configured per tenant (custom fields, optional features, role-based access overrides) and cannot be hard-coded - you MUST call this tool first, then build args to match the returned schema before invoking the target tool. The remaining mutation tools declare args inline in their own input schema, so building a payload for them needs no preparatory call; request one of those here only to obtain its richtext_format block.
The returned schema is the same one the server uses for validation, so any payload that satisfies it will pass server-side validation. Tenant config can change between sessions; do not cache results across conversations.
See Building args for Write Tools on the Working with the Tools page.
How To Enable
Go to
UsersSelect the user you would like to provide access to this tool
Click on
Access > MCPClick on
Add ToolsSelect the tool
get_args_schema_for_tooland clickAdd
Example Prompts
What fields do I need to create a vulnerability?
Show me the schema for creating a project.
What does the payload for patching a writeup look like?
Which fields are required to create a project request?
What richtext format should I use for a remediation note?
Parameters
tool
string
Yes
The mutation tool whose args schema you need. Must be one of the values listed below - read-only tools have static schemas and are not valid here.
Dynamic-shape tools (you MUST call this before building args):
Inline-schema tools (accepted here, but only needed to fetch richtext_format):
Example Response
Last updated