Title49/100
Not provided
Add a human-readable title so users do not have to interpret the tool identifier.
Description98/100
Present a secure API-credential form in the owning agent's private main chat. Use for an API outside the connected-app catalog. Supply the API HTTPS origin and authentication header fields, never secret values. Saving assigns the connection and resumes the chat. Only API credentials are supported; website passwords, cookies and browser login are excluded. Do not use ordinary input questions for credentials or ask the user to paste them into chat. Finish after presenting the card.
The description explains the capability, when to use it, and what to expect.
Inputs11/100
1 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
name
Not provided
Missing description. Explain what this value means and how to supply it.
reason
Not provided
Missing description. Explain what this value means and how to supply it.
config › origin
Exact API HTTPS origin, e.g. https://api.example.com. No paths, ports or wildcards.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
config › fields › items › key
Not provided
Missing description. Explain what this value means and how to supply it.
config › fields › items › label
Not provided
Missing description. Explain what this value means and how to supply it.
config › fields › items › header
Not provided
Missing description. Explain what this value means and how to supply it.
config › fields › items › bearer
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations0/100
Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.
Not declared
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared