other Static interface comparison
SmartBear MCP
0.42.0 0.43.0
111 schema changes require review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 7Added tools
- 0Removed tools
- 114Modified tools
- 4Input-schema changes
- 107Output-schema changes
- 0Declared authority changes
121 tools with recorded changes
bearq_get_workflow_runAddedWhat changed
- New read-only tool bearq_get_workflow_run.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
runIdnot present integer, exclusiveMinimum=0, maximum=9007199254740991required - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
bearq_list_workflowsAddedWhat changed
- New read-only tool bearq_list_workflows.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
bearq_run_workflowAddedWhat changed
- New read-only tool bearq_run_workflow.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
workflownot present string, minLength=1required - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
bearq_stop_taskModifiedWhat changed
- bearq_stop_task: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousCancels a running task. **Toolset:** Tasks **Parameters:** - taskId (number) *required*: BearQ task ID to cancel.
- CurrentCancels a pending or running task, returning { taskId, stopped: true }. The public API accepts a stop of an already-finished task as a success no-op, so this does not guarantee the task was running — check the task's status separately if that matters. **Toolset:** Tasks **Parameters:** - taskId (number) *required*: BearQ task ID to cancel.
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)taskId
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
bearq_stop_workflow_runAddedWhat changed
- New read-only tool bearq_stop_workflow_run.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
runIdnot present integer, exclusiveMinimum=0, maximum=9007199254740991required - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_add_label_to_pacticipantModifiedWhat changed
- contract-testing_add_label_to_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)labelNamepacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pacticipantnot present object, additionalProperties {…}optional - Added
_links › pacticipant › hrefnot present stringoptional - Added
_links › pacticipant › namenot present stringoptional - Added
_links › pacticipant › titlenot present stringoptional - Added
_links › selfnot present object, additionalProperties {…}optional - Added
_links › self › hrefnot present stringoptional - Added
_links › self › namenot present stringoptional - Added
_links › self › titlenot present stringoptional - Added
createdAtnot present stringoptional - Added
namenot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_add_role_to_userModifiedWhat changed
- contract-testing_admin_add_role_to_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)roleIduserId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_create_roleModifiedWhat changed
- contract-testing_admin_create_role — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)descriptionnamepermissionspermissions › [items]permissions › [items] › scope
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
creatednot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
namenot present stringoptional - Added
permissionsnot present arrayoptional - Added
permissions › [items]not present $ref="#/$defs/Permission" - Added
systemDefinednot present booleanoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_create_system_accountModifiedWhat changed
- contract-testing_admin_create_system_account — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)name
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/UserRole" - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/UserTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:tokensnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
activenot present booleanoptional - Added
authenticationSourcenot present stringoptional - Added
createdAtnot present stringoptional - Added
emailnot present stringoptional - Added
externalIdnot present stringoptional - Added
externalIdpIdnot present stringoptional - Added
externalIdpUsernamenot present stringoptional - Added
firstNamenot present stringoptional - Added
identityProviderIdnot present stringoptional - Added
lastLoginnot present stringoptional - Added
lastNamenot present stringoptional - Added
lastTimeTokenAccessednot present stringoptional - Added
namenot present stringoptional - Added
seatTypenot present stringoptional - Added
typenot present anyOf (2)optional - Added
typeDescriptionnot present stringoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_create_teamModifiedWhat changed
- contract-testing_admin_create_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
8 unchanged entries
(schema root)administratorUuidsadministratorUuids › [items]environmentUuidsenvironmentUuids › [items]namepacticipantNamespacticipantNames › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › administratorsnot present arrayoptional - Added
_embedded › administrators › [items]not present $ref="#/$defs/EmbeddedUser" - Added
_embedded › environmentsnot present arrayoptional - Added
_embedded › environments › [items]not present $ref="#/$defs/EmbeddedEnvironment" - Added
_embedded › pacticipantsnot present arrayoptional - Added
_embedded › pacticipants › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
namenot present stringoptional - Added
numberOfMembersnot present numberoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_create_userModifiedWhat changed
- contract-testing_admin_create_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)emailexternalIdpIdexternalIdpUsernamefirstNamelastNamename
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/UserRole" - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/UserTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:tokensnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
activenot present booleanoptional - Added
authenticationSourcenot present stringoptional - Added
createdAtnot present stringoptional - Added
emailnot present stringoptional - Added
externalIdnot present stringoptional - Added
externalIdpIdnot present stringoptional - Added
externalIdpUsernamenot present stringoptional - Added
firstNamenot present stringoptional - Added
identityProviderIdnot present stringoptional - Added
lastLoginnot present stringoptional - Added
lastNamenot present stringoptional - Added
lastTimeTokenAccessednot present stringoptional - Added
namenot present stringoptional - Added
seatTypenot present stringoptional - Added
typenot present anyOf (2)optional - Added
typeDescriptionnot present stringoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_delete_roleModifiedWhat changed
- contract-testing_admin_delete_role — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)roleId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_delete_teamModifiedWhat changed
- contract-testing_admin_delete_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)teamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_delete_userModifiedWhat changed
- contract-testing_admin_delete_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)userId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_get_roleModifiedWhat changed
- contract-testing_admin_get_role — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)roleId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
creatednot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
namenot present stringoptional - Added
permissionsnot present arrayoptional - Added
permissions › [items]not present $ref="#/$defs/Permission" - Added
systemDefinednot present booleanoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_get_system_account_tokensModifiedWhat changed
- contract-testing_admin_get_system_account_tokens — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)accountIdpageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › itemsnot present arrayoptional - Added
_embedded › items › [items]not present $ref="#/$defs/Token" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_get_teamModifiedWhat changed
- contract-testing_admin_get_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)teamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › administratorsnot present arrayoptional - Added
_embedded › administrators › [items]not present $ref="#/$defs/EmbeddedUser" - Added
_embedded › environmentsnot present arrayoptional - Added
_embedded › environments › [items]not present $ref="#/$defs/EmbeddedEnvironment" - Added
_embedded › membersnot present arrayoptional - Added
_embedded › members › [items]not present $ref="#/$defs/EmbeddedTeamUser" - Added
_embedded › pacticipantsnot present arrayoptional - Added
_embedded › pacticipants › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
isDefaultnot present booleanoptional - Added
namenot present stringoptional - Added
numberOfMembersnot present numberoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_get_team_userModifiedWhat changed
- contract-testing_admin_get_team_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)teamIduserId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › usernot present $ref="#/$defs/User"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_get_userModifiedWhat changed
- contract-testing_admin_get_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)userId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/UserRole" - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/UserTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:tokensnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
activenot present booleanoptional - Added
authenticationSourcenot present stringoptional - Added
createdAtnot present stringoptional - Added
emailnot present stringoptional - Added
externalIdnot present stringoptional - Added
externalIdpIdnot present stringoptional - Added
externalIdpUsernamenot present stringoptional - Added
firstNamenot present stringoptional - Added
identityProviderIdnot present stringoptional - Added
lastLoginnot present stringoptional - Added
lastNamenot present stringoptional - Added
lastTimeTokenAccessednot present stringoptional - Added
namenot present stringoptional - Added
seatTypenot present stringoptional - Added
typenot present anyOf (2)optional - Added
typeDescriptionnot present stringoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_invite_usersModifiedWhat changed
- contract-testing_admin_invite_users — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)usersusers › [items]users › [items] › emailusers › [items] › name
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
usersnot present arrayoptional - Added
users › [items]not present $ref="#/$defs/User" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_list_permissionsModifiedWhat changed
- contract-testing_admin_list_permissions — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
permissionsnot present arrayoptional - Added
permissions › [items]not present $ref="#/$defs/Permission" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_list_rolesModifiedWhat changed
- contract-testing_admin_list_roles — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/Role" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:resetnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_list_team_usersModifiedWhat changed
- contract-testing_admin_list_team_users — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pageNumberpageSizeteamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › usersnot present arrayoptional - Added
_embedded › users › [items]not present $ref="#/$defs/EmbeddedTeamUser" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_list_teamsModifiedWhat changed
- contract-testing_admin_list_teams — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pageqsize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
teamsnot present arrayoptional - Added
teams › [items]not present $ref="#/$defs/TeamInCollection" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_list_usersModifiedWhat changed
- contract-testing_admin_list_users — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)activepageqsizeuserType
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
usersnot present arrayoptional - Added
users › [items]not present $ref="#/$defs/User" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_patch_team_usersModifiedWhat changed
- contract-testing_admin_patch_team_users — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
8 unchanged entries
(schema root)operationsoperations › [items]operations › [items] › opoperations › [items] › pathoperations › [items] › valueoperations › [items] › value › uuidteamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › usersnot present arrayoptional - Added
_embedded › users › [items]not present $ref="#/$defs/EmbeddedTeamUser" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_remove_role_from_userModifiedWhat changed
- contract-testing_admin_remove_role_from_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)roleIduserId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_remove_user_from_teamModifiedWhat changed
- contract-testing_admin_remove_user_from_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)teamIduserId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_reset_rolesModifiedWhat changed
- contract-testing_admin_reset_roles — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/Role" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:resetnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_set_team_usersModifiedWhat changed
- contract-testing_admin_set_team_users — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)teamIduuidsuuids › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › usersnot present arrayoptional - Added
_embedded › users › [items]not present $ref="#/$defs/EmbeddedTeamUser" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_set_user_rolesModifiedWhat changed
- contract-testing_admin_set_user_roles — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)rolesroles › [items]userId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_update_roleModifiedWhat changed
- contract-testing_admin_update_role — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)descriptionnamepermissionspermissions › [items]permissions › [items] › scoperoleId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
creatednot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
namenot present stringoptional - Added
permissionsnot present arrayoptional - Added
permissions › [items]not present $ref="#/$defs/Permission" - Added
systemDefinednot present booleanoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_update_teamModifiedWhat changed
- contract-testing_admin_update_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
9 unchanged entries
(schema root)administratorUuidsadministratorUuids › [items]environmentUuidsenvironmentUuids › [items]namepacticipantNamespacticipantNames › [items]teamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › administratorsnot present arrayoptional - Added
_embedded › administrators › [items]not present $ref="#/$defs/EmbeddedUser" - Added
_embedded › environmentsnot present arrayoptional - Added
_embedded › environments › [items]not present $ref="#/$defs/EmbeddedEnvironment" - Added
_embedded › pacticipantsnot present arrayoptional - Added
_embedded › pacticipants › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
namenot present stringoptional - Added
numberOfMembersnot present numberoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_admin_update_userModifiedWhat changed
- contract-testing_admin_update_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)activeemailfirstNamelastNamenameuserId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/UserRole" - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/UserTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:tokensnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
activenot present booleanoptional - Added
authenticationSourcenot present stringoptional - Added
createdAtnot present stringoptional - Added
emailnot present stringoptional - Added
externalIdnot present stringoptional - Added
externalIdpIdnot present stringoptional - Added
externalIdpUsernamenot present stringoptional - Added
firstNamenot present stringoptional - Added
identityProviderIdnot present stringoptional - Added
lastLoginnot present stringoptional - Added
lastNamenot present stringoptional - Added
lastTimeTokenAccessednot present stringoptional - Added
namenot present stringoptional - Added
seatTypenot present stringoptional - Added
typenot present anyOf (2)optional - Added
typeDescriptionnot present stringoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_can_i_deployModifiedWhat changed
- contract-testing_can_i_deploy — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)environmentpacticipantversion
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
matrixnot present arrayoptional - Added
matrix › [items]not present object, additionalProperties {…} - Added
matrix › [items] › consumernot present $ref="#/$defs/MatrixPacticipant"optional - Added
matrix › [items] › pactnot present object, additionalProperties {…}optional - Added
matrix › [items] › pact › _linksnot present object, additionalProperties {…}optional - Added
matrix › [items] › pact › _links › pfi:uinot present $ref="#/$defs/EmbeddedLink"optional - Added
matrix › [items] › pact › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
matrix › [items] › pact › createdAtnot present stringoptional - Added
matrix › [items] › providernot present $ref="#/$defs/MatrixPacticipant"optional - Added
matrix › [items] › verificationResultnot present anyOf (2)optional - Added
noticesnot present arrayoptional - Added
notices › [items]not present $ref="#/$defs/Notice" - Added
summarynot present object, additionalProperties {…}optional - Added
summary › deployablenot present boolean | nulloptional - Added
summary › failednot present numberoptional - Added
summary › reasonnot present stringoptional - Added
summary › successnot present numberoptional - Added
summary › unknownnot present numberoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_check_pactflow_ai_entitlementsModifiedWhat changed
- contract-testing_check_pactflow_ai_entitlements — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
aiEnablednot present booleanoptional - Added
organizationEntitlementsnot present object, additionalProperties {…}optional - Added
userEntitlementsnot present object, additionalProperties {…}optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_create_environmentModifiedWhat changed
- contract-testing_create_environment — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)displayNamenameproductionteamUuidsteamUuids › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:currently-deployed-deployed-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:currently-supported-released-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:environmentsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
contactsnot present arrayoptional - Added
contacts › [items]not present $ref="#/$defs/Contact" - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
isDefaultnot present booleanoptional - Added
namenot present stringoptional - Added
productionnot present booleanoptional - Added
teamUuidsnot present arrayoptional - Added
teamUuids › [items]not present string - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_create_pacticipantModifiedWhat changed
- contract-testing_create_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)displayNamemainBranchnamerepositoryNamerepositoryNamespacerepositoryUrl
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › labelsnot present arrayoptional - Added
_embedded › labels › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_embedded › latest-versionnot present object, additionalProperties {…}optional - Added
_embedded › latest-version › namenot present stringoptional - Added
_embedded › latest-version › numbernot present stringoptional - Added
_embedded › latest-version › titlenot present stringoptional - Added
_embedded › latestVersionnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _linksnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_embedded › latestVersion › numbernot present stringoptional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:branch-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:branchesnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-branch-to-environment-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:teamsnot present arrayoptional - Added
_links › pb:teams › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:version-tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
mainBranchnot present stringoptional - Added
namenot present stringoptional - Added
repositoryNamenot present stringoptional - Added
repositoryNamespacenot present stringoptional - Added
repositoryUrlnot present stringoptional - Added
titlenot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_create_secretModifiedWhat changed
- contract-testing_create_secret — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)descriptionnameteamUuidvalue
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/Team"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
descriptionnot present string | nulloptional - Added
namenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_create_webhookModifiedWhat changed
- contract-testing_create_webhook — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
18 unchanged entries
(schema root)consumerconsumer › namedescriptionenabledeventsevents › [items]events › [items] › nameproviderprovider › namerequestrequest › bodyrequest › headersrequest › methodrequest › passwordrequest › urlrequest › usernameteamUuid
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/EmbeddedTeam"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:executenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:providernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
consumernot present object, additionalProperties {…}optional - Added
consumer › namenot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
enablednot present booleanoptional - Added
eventsnot present arrayoptional - Added
events › [items]not present object, additionalProperties {…} - Added
events › [items] › namenot present stringoptional - Added
providernot present object, additionalProperties {…}optional - Added
provider › namenot present stringoptional - Added
requestnot present object, additionalProperties {…}optional - Added
request › bodynot present {}optional - Added
request › headersnot present object, additionalProperties {…}optional - Added
request › methodnot present stringoptional - Added
request › passwordnot present stringoptional - Added
request › urlnot present stringoptional - Added
request › usernamenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_all_integrationsModifiedWhat changed
- contract-testing_delete_all_integrations — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_branchModifiedWhat changed
- contract-testing_delete_branch — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)branchNamepacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_environmentModifiedWhat changed
- contract-testing_delete_environment — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)environmentId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_integrationModifiedWhat changed
- contract-testing_delete_integration — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)consumerNameproviderName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_pacticipantModifiedWhat changed
- contract-testing_delete_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)pacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_secretModifiedWhat changed
- contract-testing_delete_secret — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)secretId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_delete_webhookModifiedWhat changed
- contract-testing_delete_webhook — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)webhookId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_execute_webhookModifiedWhat changed
- contract-testing_execute_webhook — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)webhookId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › try-againnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › webhooknot present $ref="#/$defs/EmbeddedLink"optional - Added
logsnot present stringoptional - Added
messagenot present stringoptional - Added
requestnot present object, additionalProperties {…}optional - Added
request › bodynot present {}optional - Added
request › headersnot present object, additionalProperties {…}optional - Added
request › urlnot present stringoptional - Added
responsenot present object, additionalProperties {…}optional - Added
response › bodynot present {}optional - Added
response › headersnot present object, additionalProperties {…}optional - Added
response › statusnot present numberoptional - Added
successnot present booleanoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_generate_pact_testsModifiedWhat changed
- contract-testing_generate_pact_tests — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
38 unchanged entries
(schema root)additionalInstructionscodecode › [items]code › [items] › bodycode › [items] › filenamecode › [items] › languagelanguageopenapiopenapi › documentopenapi › document › componentsopenapi › document › openapiopenapi › document › pathsopenapi › document › swaggeropenapi › matcheropenapi › matcher › methodsopenapi › matcher › methods › [items]openapi › matcher › operationIdopenapi › matcher › pathopenapi › matcher › statusCodesopenapi › matcher › statusCodes › [items]openapi › remoteDocumentopenapi › remoteDocument › authSchemeopenapi › remoteDocument › authTokenopenapi › remoteDocument › urlrequestResponserequestResponse › requestrequestResponse › request › bodyrequestResponse › request › filenamerequestResponse › request › languagerequestResponse › responserequestResponse › response › bodyrequestResponse › response › filenamerequestResponse › response › languagetestTemplatetestTemplate › bodytestTemplate › filenametestTemplate › language
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
codenot present stringoptional - Added
idnot present string | nulloptional - Added
instructionsnot present stringoptional - Added
languagenot present stringoptional - Added
promptnot present stringoptional - Added
requiresPromptExecutionnot present boolean, const=trueoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_audit_logModifiedWhat changed
- contract-testing_get_audit_log — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
8 unchanged entries
(schema root)frompageNumberpageSizesincesorttypeuserUuid
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present object, additionalProperties {…}optional - Added
_links › next › hrefnot present stringoptional - Added
_links › next › namenot present stringoptional - Added
_links › next › templatednot present booleanoptional - Added
_links › next › titlenot present stringoptional - Added
_links › previousnot present object, additionalProperties {…}optional - Added
_links › previous › hrefnot present stringoptional - Added
_links › previous › namenot present stringoptional - Added
_links › previous › templatednot present booleanoptional - Added
_links › previous › titlenot present stringoptional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
eventsnot present arrayoptional - Added
events › [items]not present anyOf (3) - Added
pagenot present object, additionalProperties {…}optional - Added
page › numbernot present numberoptional - Added
page › sizenot present numberoptional - Added
page › totalElementsnot present numberoptional - Added
page › totalPagesnot present numberoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_consumer_by_consumer_versionModifiedWhat changed
- contract-testing_get_bdct_consumer_by_consumer_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)consumerNameconsumerVersionNumberpageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractnot present $ref="#/$defs/ConsumerContract"optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/CrossContractVerificationResultsInConsumerContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_consumer_contract_verification_resultsModifiedWhat changed
- contract-testing_get_bdct_consumer_contract_verification_results — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_consumer_contractsModifiedWhat changed
- contract-testing_get_bdct_consumer_contracts — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractnot present $ref="#/$defs/ConsumerContract"optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/CrossContractVerificationResultsInConsumerContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_consumer_pact_test_results_by_consumerModifiedWhat changed
- contract-testing_get_bdct_consumer_pact_test_results_by_consumer — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)consumerNameconsumerVersionNumberpageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_cross-contract_verification_resultsModifiedWhat changed
- contract-testing_get_bdct_cross-contract_verification_results — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/CrossContractVerificationResultsInConsumerContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_provider_by_consumer_versionModifiedWhat changed
- contract-testing_get_bdct_provider_by_consumer_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)consumerNameconsumerVersionNumberpageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractnot present $ref="#/$defs/ProviderContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/ProviderContractVerificationResultsInProviderContract"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_provider_check_results_by_consumerModifiedWhat changed
- contract-testing_get_bdct_provider_check_results_by_consumer — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)consumerNameconsumerVersionNumberpageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/ProviderContractVerificationResultsInProviderContract"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_provider_contractModifiedWhat changed
- contract-testing_get_bdct_provider_contract — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractnot present $ref="#/$defs/ProviderContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/ProviderContractVerificationResultsInProviderContract"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_provider_contract_verification_resultsModifiedWhat changed
- contract-testing_get_bdct_provider_contract_verification_results — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/ProviderContractVerificationResultsInProviderContract"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_bdct_x-contract_test_results_by_consumerModifiedWhat changed
- contract-testing_get_bdct_x-contract_test_results_by_consumer — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)consumerNameconsumerVersionNumberpageNumberpageSizeproviderNameproviderVersionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_actionsnot present arrayoptional - Added
_actions › [items]not present $ref="#/$defs/Action" - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › consumerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › consumerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_embedded › crossContractVerificationResultsnot present $ref="#/$defs/CrossContractVerificationResultsInConsumerContract"optional - Added
_embedded › providerContractVerificationResultsnot present $ref="#/$defs/VerificationSuccess"optional - Added
_embedded › providerVersionnot present $ref="#/$defs/PacticipantVersionWithoutLinks"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
verificationStatusnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_branchModifiedWhat changed
- contract-testing_get_branch — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)branchNamepacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:latest-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
namenot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_branch_versionsModifiedWhat changed
- contract-testing_get_branch_versions — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)branchNamepacticipantNamepageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › versionsnot present arrayoptional - Added
_embedded › versions › [items]not present $ref="#/$defs/PacticipantVersionInCollection" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present arrayoptional - Added
_links › pb:versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present arrayoptional - Added
_links › versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_current_userModifiedWhat changed
- contract-testing_get_current_user — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › rolesnot present arrayoptional - Added
_embedded › roles › [items]not present $ref="#/$defs/UserRole" - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/UserTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pf:tokensnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
activenot present booleanoptional - Added
authenticationSourcenot present stringoptional - Added
createdAtnot present stringoptional - Added
emailnot present stringoptional - Added
externalIdnot present stringoptional - Added
externalIdpIdnot present stringoptional - Added
externalIdpUsernamenot present stringoptional - Added
firstNamenot present stringoptional - Added
identityProviderIdnot present stringoptional - Added
lastLoginnot present stringoptional - Added
lastNamenot present stringoptional - Added
lastTimeTokenAccessednot present stringoptional - Added
namenot present stringoptional - Added
seatTypenot present stringoptional - Added
typenot present anyOf (2)optional - Added
typeDescriptionnot present stringoptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_currently_deployed_versionsModifiedWhat changed
- contract-testing_get_currently_deployed_versions — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)environmentIdpageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › deployedVersionsnot present arrayoptional - Added
_embedded › deployedVersions › [items]not present $ref="#/$defs/EmbeddedDeployedVersion" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_currently_supported_versionsModifiedWhat changed
- contract-testing_get_currently_supported_versions — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)environmentIdpageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › releasedVersionsnot present arrayoptional - Added
_embedded › releasedVersions › [items]not present $ref="#/$defs/EmbeddedReleasedVersion" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_deployed_versions_for_versionModifiedWhat changed
- contract-testing_get_deployed_versions_for_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)environmentIdpacticipantNamepageNumberpageSizeversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › deployedVersionsnot present arrayoptional - Added
_embedded › deployedVersions › [items]not present $ref="#/$defs/EmbeddedDeployedVersion" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_environmentModifiedWhat changed
- contract-testing_get_environment — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)environmentId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:currently-deployed-deployed-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:currently-supported-released-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:environmentsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
contactsnot present arrayoptional - Added
contacts › [items]not present $ref="#/$defs/Contact" - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
isDefaultnot present booleanoptional - Added
namenot present stringoptional - Added
productionnot present booleanoptional - Added
teamUuidsnot present arrayoptional - Added
teamUuids › [items]not present string - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_integrations_by_teamModifiedWhat changed
- contract-testing_get_integrations_by_team — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pageNumberpageSizeteamId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › integrationsnot present arrayoptional - Added
_embedded › integrations › [items]not present $ref="#/$defs/Integration" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_latest_pacticipant_versionModifiedWhat changed
- contract-testing_get_latest_pacticipant_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pacticipantNametag
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › branchVersionsnot present arrayoptional - Added
_embedded › branchVersions › [items]not present $ref="#/$defs/EmbeddedBranchVersion" - Added
_embedded › deployedVersionsnot present arrayoptional - Added
_embedded › deployedVersions › [items]not present $ref="#/$defs/EmbeddedDeployedVersion" - Added
_embedded › releasedVersionsnot present arrayoptional - Added
_embedded › releasedVersions › [items]not present $ref="#/$defs/EmbeddedReleasedVersion" - Added
_embedded › tagsnot present arrayoptional - Added
_embedded › tags › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:latest-verification-results-where-pacticipant-is-consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-versionsnot present arrayoptional - Added
_links › pb:pact-versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:record-deploymentnot present arrayoptional - Added
_links › pb:record-deployment › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:record-releasenot present arrayoptional - Added
_links › pb:record-release › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
buildUrlnot present stringoptional - Added
createdAtnot present stringoptional - Added
numbernot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_metricsModifiedWhat changed
- contract-testing_get_metrics — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
crossContractComparisonsnot present object, additionalProperties {…}optional - Added
crossContractComparisons › countnot present numberoptional - Added
deployedVersionsnot present object, additionalProperties {…}optional - Added
deployedVersions › countnot present numberoptional - Added
deployedVersions › currentlyDeployedCountnot present numberoptional - Added
deployedVersions › userCreatedCountnot present numberoptional - Added
environmentsnot present object, additionalProperties {…}optional - Added
environments › countnot present numberoptional - Added
integrationsnot present object, additionalProperties {…}optional - Added
integrations › countnot present numberoptional - Added
interactionsnot present object, additionalProperties {…}optional - Added
interactions › latestInteractionsAndMessagesCountnot present numberoptional - Added
interactions › latestInteractionsCountnot present numberoptional - Added
interactions › latestMessagesCountnot present numberoptional - Added
matrixnot present object, additionalProperties {…}optional - Added
matrix › countnot present numberoptional - Added
pactPublicationsnot present object, additionalProperties {…}optional - Added
pactPublications › countnot present numberoptional - Added
pactPublications › firstnot present string | nulloptional - Added
pactPublications › lastnot present string | nulloptional - Added
pactRevisionsPerConsumerVersionnot present object, additionalProperties {…}optional - Added
pactRevisionsPerConsumerVersion › distributionnot present object, additionalProperties {…}optional - Added
pactVersionsnot present object, additionalProperties {…}optional - Added
pactVersions › countnot present numberoptional - Added
pacticipantVersionsnot present object, additionalProperties {…}optional - Added
pacticipantVersions › countnot present numberoptional - Added
pacticipantVersions › withBranchCountnot present numberoptional - Added
pacticipantVersions › withBranchSetCountnot present numberoptional - Added
pacticipantVersions › withUserCreatedBranchCountnot present numberoptional - Added
pacticipantsnot present object, additionalProperties {…}optional - Added
pacticipants › countnot present numberoptional - Added
pacticipants › withMainBranchSetCountnot present numberoptional - Added
providerContractPublicationsnot present object, additionalProperties {…}optional - Added
providerContractPublications › countnot present numberoptional - Added
providerContractSelfVerificationsnot present object, additionalProperties {…}optional - Added
providerContractSelfVerifications › countnot present numberoptional - Added
providerContractVersionsnot present object, additionalProperties {…}optional - Added
providerContractVersions › countnot present numberoptional - Added
releasedVersionsnot present object, additionalProperties {…}optional - Added
releasedVersions › countnot present numberoptional - Added
releasedVersions › currentlySupportedCountnot present numberoptional - Added
secretsnot present object, additionalProperties {…}optional - Added
secrets › countnot present numberoptional - Added
secrets › countsByTeamnot present arrayoptional - Added
secrets › countsByTeam › [items]not present number - Added
tagsnot present object, additionalProperties {…}optional - Added
tags › countnot present numberoptional - Added
tags › distinctCountnot present numberoptional - Added
tags › distinctWithPacticipantCountnot present numberoptional - Added
teamsnot present object, additionalProperties {…}optional - Added
teams › countnot present numberoptional - Added
triggeredWebhooksnot present object, additionalProperties {…}optional - Added
triggeredWebhooks › countnot present numberoptional - Added
usersnot present object, additionalProperties {…}optional - Added
users › activeRegularCountnot present numberoptional - Added
users › activeSystemCountnot present numberoptional - Added
verificationResultsnot present object, additionalProperties {…}optional - Added
verificationResults › countnot present numberoptional - Added
verificationResults › distinctCountnot present numberoptional - Added
verificationResults › failureCountnot present numberoptional - Added
verificationResults › firstnot present string | nulloptional - Added
verificationResults › lastnot present string | nulloptional - Added
verificationResults › successCountnot present numberoptional - Added
verificationResultsPerPactVersionnot present object, additionalProperties {…}optional - Added
verificationResultsPerPactVersion › distributionnot present object, additionalProperties {…}optional - Added
webhookExecutionsnot present object, additionalProperties {…}optional - Added
webhookExecutions › countnot present numberoptional - Added
webhooksnot present object, additionalProperties {…}optional - Added
webhooks › countnot present numberoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_pacticipantModifiedWhat changed
- contract-testing_get_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)pacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › labelsnot present arrayoptional - Added
_embedded › labels › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_embedded › latest-versionnot present object, additionalProperties {…}optional - Added
_embedded › latest-version › namenot present stringoptional - Added
_embedded › latest-version › numbernot present stringoptional - Added
_embedded › latest-version › titlenot present stringoptional - Added
_embedded › latestVersionnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _linksnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_embedded › latestVersion › numbernot present stringoptional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:branch-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:branchesnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-branch-to-environment-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:teamsnot present arrayoptional - Added
_links › pb:teams › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:version-tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
mainBranchnot present stringoptional - Added
namenot present stringoptional - Added
repositoryNamenot present stringoptional - Added
repositoryNamespacenot present stringoptional - Added
repositoryUrlnot present stringoptional - Added
titlenot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_pacticipant_labelModifiedWhat changed
- contract-testing_get_pacticipant_label — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)labelNamepacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pacticipantnot present object, additionalProperties {…}optional - Added
_links › pacticipant › hrefnot present stringoptional - Added
_links › pacticipant › namenot present stringoptional - Added
_links › pacticipant › titlenot present stringoptional - Added
_links › selfnot present object, additionalProperties {…}optional - Added
_links › self › hrefnot present stringoptional - Added
_links › self › namenot present stringoptional - Added
_links › self › titlenot present stringoptional - Added
createdAtnot present stringoptional - Added
namenot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_pacticipant_networkModifiedWhat changed
- contract-testing_get_pacticipant_network — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pacticipantNamepageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
integrationsnot present arrayoptional - Added
integrations › [items]not present object, additionalProperties {…} - Added
integrations › [items] › consumernot present object, additionalProperties {…}optional - Added
integrations › [items] › consumer › namenot present stringoptional - Added
integrations › [items] › providernot present object, additionalProperties {…}optional - Added
integrations › [items] › provider › namenot present stringoptional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_pacticipant_versionModifiedWhat changed
- contract-testing_get_pacticipant_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pacticipantNameversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › branchVersionsnot present arrayoptional - Added
_embedded › branchVersions › [items]not present $ref="#/$defs/EmbeddedBranchVersion" - Added
_embedded › deployedVersionsnot present arrayoptional - Added
_embedded › deployedVersions › [items]not present $ref="#/$defs/EmbeddedDeployedVersion" - Added
_embedded › releasedVersionsnot present arrayoptional - Added
_embedded › releasedVersions › [items]not present $ref="#/$defs/EmbeddedReleasedVersion" - Added
_embedded › tagsnot present arrayoptional - Added
_embedded › tags › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:latest-verification-results-where-pacticipant-is-consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-versionsnot present arrayoptional - Added
_links › pb:pact-versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:record-deploymentnot present arrayoptional - Added
_links › pb:record-deployment › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:record-releasenot present arrayoptional - Added
_links › pb:record-release › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
buildUrlnot present stringoptional - Added
createdAtnot present stringoptional - Added
numbernot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_pacts_for_verificationModifiedWhat changed
- contract-testing_get_pacts_for_verification — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
20 unchanged entries
(schema root)consumerVersionSelectorsconsumerVersionSelectors › [items]consumerVersionSelectors › [items] › branchconsumerVersionSelectors › [items] › consumerconsumerVersionSelectors › [items] › deployedconsumerVersionSelectors › [items] › deployedOrReleasedconsumerVersionSelectors › [items] › environmentconsumerVersionSelectors › [items] › fallbackBranchconsumerVersionSelectors › [items] › latestconsumerVersionSelectors › [items] › mainBranchconsumerVersionSelectors › [items] › matchingBranchconsumerVersionSelectors › [items] › releasedconsumerVersionSelectors › [items] › tagincludePendingStatusincludeWipPactsSinceproviderNameproviderVersionBranchproviderVersionTagsproviderVersionTags › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › pactsnot present arrayoptional - Added
_embedded › pacts › [items]not present $ref="#/$defs/VerifiablePact" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_provider_statesModifiedWhat changed
- contract-testing_get_provider_states — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pageNumberpageSizeprovider
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
providerStatesnot present arrayrequired - Added
providerStates › [items]not present object, additionalProperties {…} - Added
providerStates › [items] › consumersnot present arrayrequired - Added
providerStates › [items] › consumers › [items]not present string - Added
providerStates › [items] › namenot present stringrequired - Added
providerStates › [items] › paramsnot present anyOf (2)optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_released_versions_for_versionModifiedWhat changed
- contract-testing_get_released_versions_for_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)environmentIdpacticipantNamepageNumberpageSizeversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › releasedVersionsnot present arrayoptional - Added
_embedded › releasedVersions › [items]not present $ref="#/$defs/EmbeddedReleasedVersion" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_secretModifiedWhat changed
- contract-testing_get_secret — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)secretId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/Team"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
descriptionnot present string | nulloptional - Added
namenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_system_preferencesModifiedWhat changed
- contract-testing_get_system_preferences — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › preferencesnot present arrayoptional - Added
_embedded › preferences › [items]not present $ref="#/$defs/Preference" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_team_metricsModifiedWhat changed
- contract-testing_get_team_metrics — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
teamsnot present arrayoptional - Added
teams › [items]not present object, additionalProperties {…} - Added
teams › [items] › metricsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › deployedVersionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › deployedVersions › countnot present numberoptional - Added
teams › [items] › metrics › deployedVersions › currentlyDeployedCountnot present numberoptional - Added
teams › [items] › metrics › environmentsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › environments › countnot present numberoptional - Added
teams › [items] › metrics › integrationsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › integrations › countnot present numberoptional - Added
teams › [items] › metrics › interactionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › interactions › latestInteractionsCountnot present numberoptional - Added
teams › [items] › metrics › interactions › latestMessagesCountnot present numberoptional - Added
teams › [items] › metrics › pactPublicationsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › pactPublications › countnot present numberoptional - Added
teams › [items] › metrics › pactPublications › firstnot present string | nulloptional - Added
teams › [items] › metrics › pactPublications › lastnot present string | nulloptional - Added
teams › [items] › metrics › pactVersionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › pactVersions › countnot present numberoptional - Added
teams › [items] › metrics › pacticipantsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › pacticipants › countnot present numberoptional - Added
teams › [items] › metrics › providerContractPublicationsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › providerContractPublications › countnot present numberoptional - Added
teams › [items] › metrics › providerContractSelfVerificationsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › providerContractSelfVerifications › countnot present numberoptional - Added
teams › [items] › metrics › providerContractVersionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › providerContractVersions › countnot present numberoptional - Added
teams › [items] › metrics › releasedVersionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › releasedVersions › countnot present numberoptional - Added
teams › [items] › metrics › releasedVersions › currentlySupportedCountnot present numberoptional - Added
teams › [items] › metrics › secretsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › secrets › countnot present numberoptional - Added
teams › [items] › metrics › triggeredWebhooksnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › triggeredWebhooks › countnot present numberoptional - Added
teams › [items] › metrics › usersnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › users › activeRegularCountnot present numberoptional - Added
teams › [items] › metrics › users › activeSystemCountnot present numberoptional - Added
teams › [items] › metrics › verificationResultsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › verificationResults › countnot present numberoptional - Added
teams › [items] › metrics › verificationResults › failureCountnot present numberoptional - Added
teams › [items] › metrics › verificationResults › firstnot present string | nulloptional - Added
teams › [items] › metrics › verificationResults › lastnot present string | nulloptional - Added
teams › [items] › metrics › verificationResults › successCountnot present numberoptional - Added
teams › [items] › metrics › webhookExecutionsnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › webhookExecutions › countnot present numberoptional - Added
teams › [items] › metrics › webhooksnot present object, additionalProperties {…}optional - Added
teams › [items] › metrics › webhooks › countnot present numberoptional - Added
teams › [items] › namenot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_user_preferencesModifiedWhat changed
- contract-testing_get_user_preferences — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › preferencesnot present arrayoptional - Added
_embedded › preferences › [items]not present $ref="#/$defs/Preference" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_get_webhookModifiedWhat changed
- contract-testing_get_webhook — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)webhookId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/EmbeddedTeam"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:executenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:providernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
consumernot present object, additionalProperties {…}optional - Added
consumer › namenot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
enablednot present booleanoptional - Added
eventsnot present arrayoptional - Added
events › [items]not present object, additionalProperties {…} - Added
events › [items] › namenot present stringoptional - Added
providernot present object, additionalProperties {…}optional - Added
provider › namenot present stringoptional - Added
requestnot present object, additionalProperties {…}optional - Added
request › bodynot present {}optional - Added
request › headersnot present object, additionalProperties {…}optional - Added
request › methodnot present stringoptional - Added
request › passwordnot present stringoptional - Added
request › urlnot present stringoptional - Added
request › usernamenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_api_tokensModifiedWhat changed
- contract-testing_list_api_tokens — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › itemsnot present arrayoptional - Added
_embedded › items › [items]not present $ref="#/$defs/Token" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_branchesModifiedWhat changed
- contract-testing_list_branches — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)pacticipantNamepageNumberpageSizeq
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › branchesnot present arrayoptional - Added
_embedded › branches › [items]not present $ref="#/$defs/Branch" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:branchesnot present arrayoptional - Added
_links › pb:branches › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_deployed_or_released_versionsAddedWhat changed
- New read-only tool contract-testing_list_deployed_or_released_versions.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
pacticipantNamenot present stringrequired - Added
pageNumbernot present number, default=1optional - Added
pageSizenot present number, default=5optional - Added
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › versionsnot present arrayoptional - Added
_embedded › versions › [items]not present $ref="#/$defs/PacticipantVersionInCollection" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present arrayoptional - Added
_links › pb:versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present arrayoptional - Added
_links › versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_environment_versionsAddedWhat changed
- New read-only tool contract-testing_list_environment_versions.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
environmentIdnot present stringrequired - Added
pacticipantNamenot present stringrequired - Added
pageNumbernot present number, default=1optional - Added
pageSizenot present number, default=5optional - Added
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › versionsnot present arrayoptional - Added
_embedded › versions › [items]not present $ref="#/$defs/PacticipantVersionInCollection" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present arrayoptional - Added
_links › pb:versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present arrayoptional - Added
_links › versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_environmentsModifiedWhat changed
- contract-testing_list_environments — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › environmentsnot present arrayoptional - Added
_embedded › environments › [items]not present $ref="#/$defs/Environment" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:environmentsnot present arrayoptional - Added
_links › pb:environments › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_integrationsModifiedWhat changed
- contract-testing_list_integrations — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › integrationsnot present arrayoptional - Added
_embedded › integrations › [items]not present $ref="#/$defs/Integration" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_labelsModifiedWhat changed
- contract-testing_list_labels — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › labelsnot present arrayoptional - Added
_embedded › labels › [items]not present $ref="#/$defs/Label" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_pacticipant_versionsModifiedWhat changed
- contract-testing_list_pacticipant_versions — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)pacticipantNamepageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › versionsnot present arrayoptional - Added
_embedded › versions › [items]not present $ref="#/$defs/PacticipantVersionInCollection" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present arrayoptional - Added
_links › pb:versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present arrayoptional - Added
_links › versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_pacticipantsModifiedWhat changed
- contract-testing_list_pacticipants — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › pacticipantsnot present arrayoptional - Added
_embedded › pacticipants › [items]not present $ref="#/$defs/Pacticipant" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantsnot present arrayoptional - Added
_links › pacticipants › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantsnot present arrayoptional - Added
_links › pb:pacticipants › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipants-with-labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pacticipantsnot present arrayoptional - Added
pacticipants › [items]not present $ref="#/$defs/Pacticipant" - Added
pagenot present $ref="#/$defs/Page"optional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_pacticipants_by_labelModifiedWhat changed
- contract-testing_list_pacticipants_by_label — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)labelNamepageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › pacticipantsnot present arrayoptional - Added
_embedded › pacticipants › [items]not present $ref="#/$defs/Pacticipant" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › nextnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pacticipantsnot present arrayoptional - Added
_links › pacticipants › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantsnot present arrayoptional - Added
_links › pb:pacticipants › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipants-with-labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › previousnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
pacticipantsnot present arrayoptional - Added
pacticipants › [items]not present $ref="#/$defs/Pacticipant" - Added
pagenot present $ref="#/$defs/Page"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_secretsModifiedWhat changed
- contract-testing_list_secrets — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › secretsnot present arrayoptional - Added
_embedded › secrets › [items]not present $ref="#/$defs/Secret" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_list_webhooksModifiedWhat changed
- contract-testing_list_webhooks — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pageNumberpageSize
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › webhooksnot present arrayoptional - Added
_embedded › webhooks › [items]not present $ref="#/$defs/EmbeddedWebhook" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:createnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:webhooksnot present arrayoptional - Added
_links › pb:webhooks › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
paginationnot present object, additionalProperties=falseoptional - Added
pagination › pageNumbernot present numberrequired - Added
pagination › pageSizenot present numberrequired - Added
pagination › totalItemsnot present numberrequired - Added
pagination › totalPagesnot present numberrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_matrixModifiedWhat changed
- contract-testing_matrix — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
12 unchanged entries
(schema root)latestbylimitqq › [items]q › [items] › branchq › [items] › environmentq › [items] › latestq › [items] › mainBranchq › [items] › pacticipantq › [items] › tagq › [items] › version
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
matrixnot present arrayoptional - Added
matrix › [items]not present object, additionalProperties {…} - Added
matrix › [items] › consumernot present $ref="#/$defs/MatrixPacticipant"optional - Added
matrix › [items] › pactnot present object, additionalProperties {…}optional - Added
matrix › [items] › pact › _linksnot present object, additionalProperties {…}optional - Added
matrix › [items] › pact › _links › pfi:uinot present $ref="#/$defs/EmbeddedLink"optional - Added
matrix › [items] › pact › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
matrix › [items] › pact › createdAtnot present stringoptional - Added
matrix › [items] › providernot present $ref="#/$defs/MatrixPacticipant"optional - Added
matrix › [items] › verificationResultnot present anyOf (2)optional - Added
noticesnot present arrayoptional - Added
notices › [items]not present $ref="#/$defs/Notice" - Added
summarynot present object, additionalProperties {…}optional - Added
summary › deployablenot present boolean | nulloptional - Added
summary › failednot present numberoptional - Added
summary › reasonnot present stringoptional - Added
summary › successnot present numberoptional - Added
summary › unknownnot present numberoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_patch_pacticipantModifiedWhat changed
- contract-testing_patch_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)displayNamemainBranchpacticipantNamerepositoryNamerepositoryNamespacerepositoryUrl
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › labelsnot present arrayoptional - Added
_embedded › labels › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_embedded › latest-versionnot present object, additionalProperties {…}optional - Added
_embedded › latest-version › namenot present stringoptional - Added
_embedded › latest-version › numbernot present stringoptional - Added
_embedded › latest-version › titlenot present stringoptional - Added
_embedded › latestVersionnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _linksnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_embedded › latestVersion › numbernot present stringoptional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:branch-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:branchesnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-branch-to-environment-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:teamsnot present arrayoptional - Added
_links › pb:teams › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:version-tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
mainBranchnot present stringoptional - Added
namenot present stringoptional - Added
repositoryNamenot present stringoptional - Added
repositoryNamespacenot present stringoptional - Added
repositoryUrlnot present stringoptional - Added
titlenot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_publish_consumer_contractsModifiedWhat changed
- contract-testing_publish_consumer_contracts — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
14 unchanged entries
(schema root)branchbuildUrlcontractscontracts › [items]contracts › [items] › consumerNamecontracts › [items] › contentcontracts › [items] › contentTypecontracts › [items] › providerNamecontracts › [items] › specificationpacticipantNamepacticipantVersionNumbertagstags › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › pacticipantnot present $ref="#/$defs/EmbeddedNamed"optional - Added
_embedded › versionnot present $ref="#/$defs/EmbeddedVersion"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:contractsnot present arrayoptional - Added
_links › pb:contracts › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipant-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipant-version-tagsnot present arrayoptional - Added
_links › pb:pacticipant-version-tags › [items]not present $ref="#/$defs/EmbeddedLink" - Added
noticesnot present arrayoptional - Added
notices › [items]not present $ref="#/$defs/Notice" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_publish_provider_contractModifiedWhat changed
- contract-testing_publish_provider_contract — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
18 unchanged entries
(schema root)branchbuildUrlcontractcontract › contentcontract › contentTypecontract › selfVerificationResultscontract › selfVerificationResults › contentcontract › selfVerificationResults › contentTypecontract › selfVerificationResults › formatcontract › selfVerificationResults › successcontract › selfVerificationResults › verifiercontract › selfVerificationResults › verifierVersioncontract › specificationpacticipantVersionNumberproviderNametagstags › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › pacticipantnot present $ref="#/$defs/EmbeddedNamed"optional - Added
_embedded › versionnot present $ref="#/$defs/EmbeddedVersion"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:branch-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipant-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pacticipant-version-tagsnot present arrayoptional - Added
_links › pb:pacticipant-version-tags › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pf:provider-contractnot present $ref="#/$defs/EmbeddedLink"optional - Added
noticesnot present arrayoptional - Added
notices › [items]not present $ref="#/$defs/Notice" - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_record_deploymentModifiedWhat changed
- contract-testing_record_deployment — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)applicationInstanceenvironmentIdpacticipantNameversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › environmentnot present $ref="#/$defs/Environment"optional - Added
_embedded › pacticipantnot present $ref="#/$defs/EmbeddedNamed"optional - Added
_embedded › versionnot present $ref="#/$defs/EmbeddedVersion"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
applicationInstancenot present stringoptional - Added
createdAtnot present stringoptional - Added
currentlyDeployednot present booleanoptional - Added
targetnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_record_releaseModifiedWhat changed
- contract-testing_record_release — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)environmentIdpacticipantNameversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › environmentnot present $ref="#/$defs/Environment"optional - Added
_embedded › pacticipantnot present $ref="#/$defs/EmbeddedNamed"optional - Added
_embedded › versionnot present $ref="#/$defs/EmbeddedVersion"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
currentlySupportednot present booleanoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_regenerate_api_tokenModifiedWhat changed
- contract-testing_regenerate_api_token — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)tokenId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:regeneratenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
descriptionnot present stringoptional - Added
expiresnot present stringoptional - Added
lastUsednot present stringoptional - Added
readOnlynot present booleanoptional - Added
uuidnot present stringoptional - Added
valuenot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_remove_label_from_pacticipantModifiedWhat changed
- contract-testing_remove_label_from_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)labelNamepacticipantName
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties=false - Added
successnot present boolean, const=truerequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_review_pact_testsModifiedWhat changed
- contract-testing_review_pact_tests — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
30 unchanged entries
(schema root)codecode › [items]code › [items] › bodycode › [items] › filenamecode › [items] › languageerrorMessageserrorMessages › [items]openapiopenapi › documentopenapi › document › componentsopenapi › document › openapiopenapi › document › pathsopenapi › document › swaggeropenapi › matcheropenapi › matcher › methodsopenapi › matcher › methods › [items]openapi › matcher › operationIdopenapi › matcher › pathopenapi › matcher › statusCodesopenapi › matcher › statusCodes › [items]openapi › remoteDocumentopenapi › remoteDocument › authSchemeopenapi › remoteDocument › authTokenopenapi › remoteDocument › urlpactTestspactTests › bodypactTests › filenamepactTests › languageuserInstructions
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, additionalProperties {…} - Added
instructionsnot present stringoptional - Added
promptnot present stringoptional - Added
recommendationsnot present arrayoptional - Added
recommendations › [items]not present object, additionalProperties {…} - Added
recommendations › [items] › confidencenot present number | nulloptional - Added
recommendations › [items] › diffnot present string | nulloptional - Added
recommendations › [items] › recommendationnot present stringrequired - Added
requiresPromptExecutionnot present boolean, const=trueoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_test_execute_webhooksModifiedWhat changed
- contract-testing_test_execute_webhooks — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › try-againnot present $ref="#/$defs/EmbeddedLink"optional - Added
logsnot present stringoptional - Added
messagenot present stringoptional - Added
requestnot present object, additionalProperties {…}optional - Added
request › bodynot present {}optional - Added
request › headersnot present object, additionalProperties {…}optional - Added
request › urlnot present stringoptional - Added
responsenot present object, additionalProperties {…}optional - Added
response › bodynot present {}optional - Added
response › headersnot present object, additionalProperties {…}optional - Added
response › statusnot present numberoptional - Added
successnot present booleanoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_update_environmentModifiedWhat changed
- contract-testing_update_environment — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)displayNameenvironmentIdnameproductionteamUuidsteamUuids › [items]
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:currently-deployed-deployed-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:currently-supported-released-versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:environmentsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
contactsnot present arrayoptional - Added
contacts › [items]not present $ref="#/$defs/Contact" - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
isDefaultnot present booleanoptional - Added
namenot present stringoptional - Added
productionnot present booleanoptional - Added
teamUuidsnot present arrayoptional - Added
teamUuids › [items]not present string - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_update_pacticipantModifiedWhat changed
- contract-testing_update_pacticipant — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)displayNamemainBranchpacticipantNamerepositoryNamerepositoryNamespacerepositoryUrl
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › labelsnot present arrayoptional - Added
_embedded › labels › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_embedded › latest-versionnot present object, additionalProperties {…}optional - Added
_embedded › latest-version › namenot present stringoptional - Added
_embedded › latest-version › numbernot present stringoptional - Added
_embedded › latest-version › titlenot present stringoptional - Added
_embedded › latestVersionnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _linksnot present object, additionalProperties {…}optional - Added
_embedded › latestVersion › _links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_embedded › latestVersion › numbernot present stringoptional - Added
_embedded › teamsnot present arrayoptional - Added
_embedded › teams › [items]not present $ref="#/$defs/EmbeddedTeam" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:branch-versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:branchesnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:can-i-deploy-branch-to-environment-badgenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:labelnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:teamsnot present arrayoptional - Added
_links › pb:teams › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:versionnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:version-tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › versionsnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
displayNamenot present stringoptional - Added
mainBranchnot present stringoptional - Added
namenot present stringoptional - Added
repositoryNamenot present stringoptional - Added
repositoryNamespacenot present stringoptional - Added
repositoryUrlnot present stringoptional - Added
titlenot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_update_pacticipant_versionModifiedWhat changed
- contract-testing_update_pacticipant_version — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)buildUrlpacticipantNameversionNumber
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › branchVersionsnot present arrayoptional - Added
_embedded › branchVersions › [items]not present $ref="#/$defs/EmbeddedBranchVersion" - Added
_embedded › deployedVersionsnot present arrayoptional - Added
_embedded › deployedVersions › [items]not present $ref="#/$defs/EmbeddedDeployedVersion" - Added
_embedded › releasedVersionsnot present arrayoptional - Added
_embedded › releasedVersions › [items]not present $ref="#/$defs/EmbeddedReleasedVersion" - Added
_embedded › tagsnot present arrayoptional - Added
_embedded › tags › [items]not present $ref="#/$defs/EmbeddedNamed" - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › curiesnot present arrayoptional - Added
_links › curies › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:latest-verification-results-where-pacticipant-is-consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-versionsnot present arrayoptional - Added
_links › pb:pact-versions › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:pacticipantnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:record-deploymentnot present arrayoptional - Added
_links › pb:record-deployment › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:record-releasenot present arrayoptional - Added
_links › pb:record-release › [items]not present $ref="#/$defs/EmbeddedLink" - Added
_links › pb:tagnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
buildUrlnot present stringoptional - Added
createdAtnot present stringoptional - Added
numbernot present stringoptional - Added
updatedAtnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_update_secretModifiedWhat changed
- contract-testing_update_secret — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)descriptionnamesecretIdvalue
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/Team"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
createdAtnot present stringoptional - Added
descriptionnot present string | nulloptional - Added
namenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
contract-testing_update_webhookModifiedWhat changed
- contract-testing_update_webhook — Output schema: schema added.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- write → write
Input schema
Input schema unchanged.
17 unchanged entries
(schema root)consumerdescriptionenabledeventsevents › [items]events › [items] › nameproviderrequestrequest › bodyrequest › headersrequest › methodrequest › passwordrequest › urlrequest › usernameteamUuidwebhookId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object, $defs {…}, additionalProperties {…} - Added
_embeddednot present object, additionalProperties {…}optional - Added
_embedded › teamnot present $ref="#/$defs/EmbeddedTeam"optional - Added
_linksnot present object, additionalProperties {…}optional - Added
_links › pb:consumernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:executenot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:pact-webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:providernot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › pb:webhooksnot present $ref="#/$defs/EmbeddedLink"optional - Added
_links › selfnot present $ref="#/$defs/EmbeddedLink"optional - Added
consumernot present object, additionalProperties {…}optional - Added
consumer › namenot present stringoptional - Added
createdAtnot present stringoptional - Added
descriptionnot present stringoptional - Added
enablednot present booleanoptional - Added
eventsnot present arrayoptional - Added
events › [items]not present object, additionalProperties {…} - Added
events › [items] › namenot present stringoptional - Added
providernot present object, additionalProperties {…}optional - Added
provider › namenot present stringoptional - Added
requestnot present object, additionalProperties {…}optional - Added
request › bodynot present {}optional - Added
request › headersnot present object, additionalProperties {…}optional - Added
request › methodnot present stringoptional - Added
request › passwordnot present stringoptional - Added
request › urlnot present stringoptional - Added
request › usernamenot present stringoptional - Added
teamUuidnot present string | nulloptional - Added
updatedAtnot present stringoptional - Added
uuidnot present stringoptional - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_bulk_update_test_case_execution_statusModifiedWhat changed
- qmetry_bulk_update_test_case_execution_status — Schema change: input property added: udfValuesByRun.
- qmetry_bulk_update_test_case_execution_status — Schema change: input property added: viewId.
- qmetry_bulk_update_test_case_execution_status: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate execution status for individual or multiple test case runs in bulk **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - entityIDs (string) *required*: Comma-separated IDs of Test Case Runs to update. CRITICAL: the parameter name is 'entityIDs' — do NOT use 'tcRunIDs', 'testCaseRunIds', 'runIds', or other variants. Accepts a number or string (e.g., 66095087 or '66095087' for single, '66095069,66095075' for bulk). To get the entityIDs - Call API 'Execution/Fetch Testcase Run ID'. From the response, get value -> data[<index>].tcRunID - entityType (enum): Type of Entity to Execute: 'TCR' (Test Case Run) or 'TCSR' (Test Case Step Run) (default: "TCR") - qmTsRunId (string) *required*: Id of Test Suite Run to execute (required). CRITICAL: the parameter name is 'qmTsRunId' — do NOT use 'tsrunID', 'testSuiteRunId', 'tsRunID', or other variants. Accepts a number or string. To get the qmTsRunId - Call API 'Execution/Fetch Executions'. From the response, get value -> data[<index>].tsRunID - runStatusID (number) *required*: Id of the execution status to set (required). To get the runStatusID - Call API 'Admin/Project GET info Service' From the response, get value of following attribute -> allstatus[<index>].id Common statuses: Pass, Fail, Not Run, Blocked, WIP, etc. - dropID (union): Unique identifier of drop/build on which execution is to be performed (optional). To get the dropID - Call API 'Fetch Build/List' From the response, get value of following attribute -> data[<index>].dropID - isAutoExecuted (enum): Set '1' for automated and '0' for manual Execution Type - isBulkOperation (boolean): Set true for bulk operations (multiple entityIDs), false for single execution update. Default: true if multiple comma-separated entityIDs, false otherwise - comments (string): Optional comments for the execution status update - username (string): If Part 11 Compliance is active then required for authentication - password (string): If Part 11 Compliance is active then required for authentication - qmRunObj (string): Internal QMetry run object (optional, usually empty string) - type (enum): Type of Entity - same as entityType (for backwards compatibility) **Output Description:** JSON object with success status, updated execution details, and confirmation message **Use Cases:** 1. Update single test case run status to Pass, Fail, Blocked, or Not Run 2. Bulk update multiple test case run statuses in a single operation 3. Mark all selected test case runs as Not Run for re-execution 4. Update execution status after manual test execution 5. Set execution status based on automated test results 6. Update test execution status across different test environments 7. Track test execution progress and completion 8. Manage test execution status for compliance and reporting **Examples:** 1. Update single test case run status to Failed (single execution) ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "isBulkOperation": false } ``` Expected Output: Test case run 66095087 status updated to Failed successfully 2. Bulk update two test case runs to Pass status (bulk execution) ```json { "entityIDs": "66095069,66095075", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123268, "isBulkOperation": true, "comments": "All test cases passed successfully" } ``` Expected Output: Test case runs 66095069 and 66095075 updated to Pass status successfully 3. Bulk update all selected test case runs to Not Run status ```json { "entityIDs": "66095069,66095075,66095081,66095087,66095093,66095099,66095105", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123269, "isBulkOperation": true } ``` Expected Output: 7 test case runs updated to Not Run status successfully for re-execution 4. Update test case run with build/drop information ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "dropID": 947, "isBulkOperation": false } ``` Expected Output: Test case run updated with execution status and build information 5. Update automated test execution status with automation flag ```json { "entityIDs": "66095069,66095075", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123268, "isAutoExecuted": "1", "isBulkOperation": true, "comments": "Automated test execution completed" } ``` Expected Output: Automated test case runs updated to Pass status with automation flag 6. Update test case run status with Part 11 Compliance authentication ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "username": "test.user", "password": "password", "isBulkOperation": false } ``` Expected Output: Test case run status updated with Part 11 Compliance authentication 7. Update ALL executions of test suite VKMC-TS-20 to Failed (MULTI-CALL OPERATION) ```json { "entityIDs": "66341841,66342887,66342893,66342899", "entityType": "TCR", "qmTsRunId": "2733104", "runStatusID": 123269, "isBulkOperation": true } ``` Expected Output: Execution 1/4 updated. The MCP Agent will automatically repeat this operation for executions 2733205, 2733306, and 2733407 using their corresponding entityIDs. **Hints:** 1. CRITICAL: entityIDs, entityType, qmTsRunId, and runStatusID are REQUIRED parameters 2. 3. CRITICAL - ALWAYS FETCH STATUS IDs FROM PROJECT INFO: 4. NEVER use hardcoded or memorized status IDs. Status IDs are PROJECT-SPECIFIC and must be fetched dynamically. 5. MANDATORY WORKFLOW BEFORE USING runStatusID: 6. 1. Call mcp_smartbear_qmetry_fetch_qmetry_project_info with the current projectKey 7. 2. Extract the 'allstatus' array from the response 8. 3. Match the desired status NAME to find its corresponding ID 9. 4. Use the fetched ID in the runStatusID parameter 10. 11. EXAMPLE STATUS ID RESOLUTION: 12. User says: 'Update status to Failed' 13. Step 1: Call FETCH_PROJECT_INFO → Get allstatus array 14. Step 2: Find status where name='Failed' → Extract its id property 15. Step 3: Use that id as runStatusID (e.g., 123269 for 'Failed') 16. 17. COMMON STATUS NAMES (IDs vary by project - MUST VALIDATE): 18. - 'Passed' / 'Pass' - Test case executed successfully 19. - 'Failed' / 'Fail' - Test case failed with errors 20. - 'Blocked' - Test case cannot be executed due to blockers 21. - 'Not Run' - Test case not yet executed or needs re-execution 22. - 'WIP' / 'Work In Progress' - Test case execution in progress 23. - 'Not Applicable' - Test case not applicable for this execution 24. 25. WHY THIS IS CRITICAL: 26. - Status IDs are assigned per QMetry project and are NOT universal 27. - Using wrong status ID will update tests with incorrect status 28. - Example: ID 123268 might be 'Blocked' in one project but 'Passed' in another 29. - The allstatus array is the AUTHORITATIVE source for all status mappings 30. 31. HOW TO GET entityIDs (Test Case Run IDs): 32. 1. Call API 'Execution/Fetch Testcase Run ID' (FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN tool) 33. 2. From the response, get value of following attribute -> data[<index>].tcRunID 34. 3. Example: Single ID '66095087' or Multiple IDs '66095069,66095075,66095081' 35. 4. For bulk operations, provide comma-separated IDs without spaces 36. HOW TO GET qmTsRunId (Test Suite Run ID): 37. 1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE tool) 38. 2. From the response, get value of following attribute -> data[<index>].tsRunID 39. 3. Example: Test Suite Run ID might be '2720260' 40. HOW TO GET runStatusID (Execution Status ID) - DETAILED PROCESS: 41. 1. Call API 'Admin/Get info Service' (FETCH_PROJECT_INFO tool) with projectKey 42. 2. From the response, locate the 'allstatus' array 43. 3. Search for the status object where name matches your desired status (case-insensitive) 44. 4. Extract the 'id' property from the matching status object 45. 5. NEVER use example IDs from documentation - they are project-specific 46. 47. EXAMPLE allstatus ARRAY STRUCTURE: 48. allstatus: [ 49. { name: 'Passed', defaultName: 'passed', id: 123266, color: '#14892C|#FFFFFF' }, 50. { name: 'Failed', defaultName: 'failed', id: 123269, color: '#FF6666|#FFFFFF' }, 51. { name: 'Blocked', defaultName: 'blocked', id: 123268, color: '#CCCCCC|#FFFFFF' }, 52. { name: 'Not Run', defaultName: 'notrun', id: 123270, color: '#205081|#FFFFFF', isdefault: true }, 53. { name: 'Not Applicable', defaultName: 'empty', id: 123267, color: '#59AFE1|#FFFFFF' } 54. ] 55. Note: Above IDs are EXAMPLES ONLY - fetch actual IDs from your project 56. HOW TO GET dropID (Build/Drop ID) - OPTIONAL: 57. 1. Call API 'Build/List' (FETCH_BUILDS tool) 58. 2. From the response, get value of following attribute -> data[<index>].dropID 59. 3. Example: Build/Drop ID might be 947 60. ENTITY TYPES: 61. - 'TCR' = Test Case Run (most common use case) 62. - 'TCSR' = Test Case Step Run (for step-level execution updates) 63. BULK OPERATION FLAG: 64. - isBulkOperation=false: Single test case run update (one entityID) 65. - isBulkOperation=true: Multiple test case runs update (comma-separated entityIDs) 66. - Auto-detected: If entityIDs contains comma, defaults to true; otherwise false 67. AUTOMATION FLAG (isAutoExecuted) - OPTIONAL: 68. - '1' = Automated execution (test run by automation framework) 69. - '0' = Manual execution (test run by human tester) 70. - Used for execution tracking and reporting purposes 71. PART 11 COMPLIANCE (username & password) - CONDITIONAL: 72. - Required ONLY if Part 11 Compliance is active in your QMetry instance 73. - Used for regulatory compliance and audit trail purposes 74. - Not needed for standard QMetry installations 75. COMMENTS FIELD - OPTIONAL: 76. - Add execution notes, failure reasons, or status change context 77. - Useful for tracking why status was changed 78. - Appears in execution history and audit logs 79. COMMON EXECUTION STATUS NAMES: 80. - Pass: Test case executed successfully 81. - Fail: Test case failed with errors 82. - Blocked: Test case cannot be executed due to blockers 83. - Not Run: Test case not yet executed or needs re-execution 84. - WIP: Work In Progress - test case execution in progress 85. WORKFLOW FOR USER PROMPTS: 86. 1. If user says 'execute test case run by id to failed' or 'update status to fail': 87. - Fetch test case runs to get tcRunID (entityIDs) 88. - Fetch project info to get 'Fail' status ID (runStatusID) 89. - Set isBulkOperation=false for single ID 90. 2. If user says 'bulk update test case run status to pass' or 'update all to passed': 91. - Fetch test case runs to get multiple tcRunIDs 92. - Fetch project info to get 'Pass' status ID 93. - Set isBulkOperation=true 94. - Join multiple IDs with commas (no spaces) 95. 3. If user says 'execute status to not run of given test case run ids': 96. - Use provided IDs or fetch if needed 97. - Fetch project info to get 'Not Run' status ID 98. - Set isBulkOperation based on ID count 99. 4. If the user requests updating status for ALL executions of a test suite, the agent must: 100. 1. Call FETCH_EXECUTIONS_BY_TESTSUITE to get all qmTsRunIds. 101. 2. For each qmTsRunId: 102. - Call FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN to get tcRunID (entityIDs) 103. - Fetch project info to get 'Fail' status ID (runStatusID) 104. - Call BULK_UPDATE_EXECUTION_STATUS with the corresponding qmTsRunId + tcRunID + desired runStatusID 105. 3. Repeat until all executions are updated. 106. This tool is intended to be invoked multiple times in sequence for multi-execution updates. 107. FIELD MAPPING CRITICAL NOTES: 108. - entityIDs must be comma-separated STRING (e.g., '66095069,66095075') 109. - qmTsRunId must be STRING format (e.g., '2720260') 110. - runStatusID must be NUMERIC (e.g., 123268) 111. - dropID can be numeric or string (flexible) 112. API ENDPOINT: PUT /rest/execution/runstatus/bulkupdate 113. This tool is essential for test execution management and status tracking 114. Critical for maintaining accurate test execution records and reporting 115. Use for manual test execution updates and automated test result integration 116. Essential for test execution audit trails and compliance requirements
- CurrentUpdate execution status for individual or multiple test case runs in bulk, enforcing mandatory Test Run UDFs **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - entityIDs (string) *required*: Comma-separated IDs of Test Case Runs to update. CRITICAL: the parameter name is 'entityIDs' — do NOT use 'tcRunIDs', 'testCaseRunIds', 'runIds', or other variants. Accepts a number or string (e.g., 66095087 or '66095087' for single, '66095069,66095075' for bulk). To get the entityIDs - Call API 'Execution/Fetch Testcase Run ID'. From the response, get value -> data[<index>].tcRunID - entityType (enum): Type of Entity to Execute: 'TCR' (Test Case Run) or 'TCSR' (Test Case Step Run) (default: "TCR") - qmTsRunId (string) *required*: Id of Test Suite Run to execute (required). CRITICAL: the parameter name is 'qmTsRunId' — do NOT use 'tsrunID', 'testSuiteRunId', 'tsRunID', or other variants. Accepts a number or string. To get the qmTsRunId - Call API 'Execution/Fetch Executions'. From the response, get value -> data[<index>].tsRunID - runStatusID (number) *required*: Id of the execution status to set (required). To get the runStatusID - Call API 'Admin/Project GET info Service' From the response, get value of following attribute -> allstatus[<index>].id Common statuses: Pass, Fail, Not Run, Blocked, WIP, etc. - dropID (union): Unique identifier of drop/build on which execution is to be performed (optional). To get the dropID - Call API 'Fetch Build/List' From the response, get value of following attribute -> data[<index>].dropID - isAutoExecuted (enum): Set '1' for automated and '0' for manual Execution Type - isBulkOperation (boolean): Set true for bulk operations (multiple entityIDs), false for single execution update. Default: true if multiple comma-separated entityIDs, false otherwise - comments (string): Optional comments for the execution status update - username (string): If Part 11 Compliance is active then required for authentication - password (string): If Part 11 Compliance is active then required for authentication - qmRunObj (string): Internal QMetry run object (optional, usually empty string) - type (enum): Type of Entity - same as entityType (for backwards compatibility) - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. - udfValuesByRun (record<string, record<string, object>>): Optional Test Run UDF values to set BEFORE the status is updated, keyed per Test Case Run. Outer key: tcRunID (must be one of entityIDs). Inner key: UDF field 'name' (e.g. 'test_env' — NOT the 'FLD.' fieldKey). Inner value: { value, fieldID?, multiSelectAction? }. Use this to fill mandatory Test Run UDFs reported by a MANDATORY_TEST_RUN_UDF_MISSING response. Example: { "66095069": { "test_env": { "value": "QA" } }, "66095075": { "test_env": { "value": "UAT" } } } **Output Description:** On success: { success: true, udfUpdates: [{ tcRunIDs, response }], statusUpdate: <API response> }. When mandatory Test Run UDFs are missing: { success: false, code: 'MANDATORY_TEST_RUN_UDF_MISSING', statusUpdated: false, runsMissingFields, lookupOptions?, _note }. **Use Cases:** 1. Update single test case run status to Pass, Fail, Blocked, or Not Run 2. Bulk update multiple test case run statuses in a single operation 3. Mark all selected test case runs as Not Run for re-execution 4. Update execution status after manual test execution 5. Set execution status based on automated test results 6. Update test execution status across different test environments 7. Track test execution progress and completion 8. Manage test execution status for compliance and reporting 9. Fill mandatory Test Run UDFs per run and update the execution status in one call **Examples:** 1. Update single test case run status to Failed (single execution) ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "isBulkOperation": false } ``` Expected Output: Test case run 66095087 status updated to Failed successfully 2. Bulk update two test case runs to Pass status (bulk execution) ```json { "entityIDs": "66095069,66095075", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123268, "isBulkOperation": true, "comments": "All test cases passed successfully" } ``` Expected Output: Test case runs 66095069 and 66095075 updated to Pass status successfully 3. Bulk update all selected test case runs to Not Run status ```json { "entityIDs": "66095069,66095075,66095081,66095087,66095093,66095099,66095105", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123269, "isBulkOperation": true } ``` Expected Output: 7 test case runs updated to Not Run status successfully for re-execution 4. Update test case run with build/drop information ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "dropID": 947, "isBulkOperation": false } ``` Expected Output: Test case run updated with execution status and build information 5. Update automated test execution status with automation flag ```json { "entityIDs": "66095069,66095075", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123268, "isAutoExecuted": "1", "isBulkOperation": true, "comments": "Automated test execution completed" } ``` Expected Output: Automated test case runs updated to Pass status with automation flag 6. Update test case run status with Part 11 Compliance authentication ```json { "entityIDs": "66095087", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123266, "username": "test.user", "password": "password", "isBulkOperation": false } ``` Expected Output: Test case run status updated with Part 11 Compliance authentication 7. Update ALL executions of test suite VKMC-TS-20 to Failed (MULTI-CALL OPERATION) ```json { "entityIDs": "66341841,66342887,66342893,66342899", "entityType": "TCR", "qmTsRunId": "2733104", "runStatusID": 123269, "isBulkOperation": true } ``` Expected Output: Execution 1/4 updated. The MCP Agent will automatically repeat this operation for executions 2733205, 2733306, and 2733407 using their corresponding entityIDs. 8. Retry after MANDATORY_TEST_RUN_UDF_MISSING: fill mandatory Test Run UDF 'test_env' per run, then mark both runs Passed ```json { "entityIDs": "66095069,66095075", "entityType": "TCR", "qmTsRunId": "2720260", "runStatusID": 123268, "isBulkOperation": true, "udfValuesByRun": { "66095069": { "test_env": { "value": "QA" } }, "66095075": { "test_env": { "value": "UAT" } } } } ``` Expected Output: { success: true, udfUpdates: [{ tcRunIDs: [66095069], ... }, { tcRunIDs: [66095075], ... }], statusUpdate: {...} } **Hints:** 1. CRITICAL: entityIDs, entityType, qmTsRunId, and runStatusID are REQUIRED parameters 2. 3. MANDATORY TEST RUN UDF GATE (entityType 'TCR', applies to EVERY target status including Not Run): 4. - Before updating, the tool checks each run's Test Run UDFs; fields with allowBlank=false are mandatory. 5. - If ANY run is missing a mandatory value, NOTHING is updated and the tool returns code 'MANDATORY_TEST_RUN_UDF_MISSING' with runsMissingFields[{ tcRunID, entityKey, missingFields[{ name, label, fieldID, fieldType, listName? }] }]. 6. - On that response: show the missing fields per run to the user, ask for the values (never invent them), then call this tool again with the same arguments plus 'udfValuesByRun'. 7. - 'udfValuesByRun' format: { '<tcRunID>': { '<udf name>': { value } } }. Keys are tcRunIDs from entityIDs; inner keys are the UDF 'name' (not the 'FLD.' fieldKey). fieldID is optional (auto-filled). 8. - Value formats: DATETIMEPICKER 'MM-DD-YYYY'; LOOKUPLIST option id (from lookupOptions[listName][].id); MULTILOOKUPLIST array of ids; CASCADINGLIST { parent, child }. 9. - Supplied UDF values are written first (Bulk Update Test Run UDFs), then the status is updated. Non-mandatory UDFs can also be set this way. 10. - entityType 'TCSR' (step runs) skips the gate; 'udfValuesByRun' is rejected for TCSR. 11. - viewId is auto-resolved (latestViews.TE.viewId); do not pass it unless you have a specific one. 12. 13. CRITICAL - ALWAYS FETCH STATUS IDs FROM PROJECT INFO: 14. NEVER use hardcoded or memorized status IDs. Status IDs are PROJECT-SPECIFIC and must be fetched dynamically. 15. MANDATORY WORKFLOW BEFORE USING runStatusID: 16. 1. Call mcp_smartbear_qmetry_fetch_qmetry_project_info with the current projectKey 17. 2. Extract the 'allstatus' array from the response 18. 3. Match the desired status NAME to find its corresponding ID 19. 4. Use the fetched ID in the runStatusID parameter 20. 21. EXAMPLE STATUS ID RESOLUTION: 22. User says: 'Update status to Failed' 23. Step 1: Call FETCH_PROJECT_INFO → Get allstatus array 24. Step 2: Find status where name='Failed' → Extract its id property 25. Step 3: Use that id as runStatusID (e.g., 123269 for 'Failed') 26. 27. COMMON STATUS NAMES (IDs vary by project - MUST VALIDATE): 28. - 'Passed' / 'Pass' - Test case executed successfully 29. - 'Failed' / 'Fail' - Test case failed with errors 30. - 'Blocked' - Test case cannot be executed due to blockers 31. - 'Not Run' - Test case not yet executed or needs re-execution 32. - 'WIP' / 'Work In Progress' - Test case execution in progress 33. - 'Not Applicable' - Test case not applicable for this execution 34. 35. WHY THIS IS CRITICAL: 36. - Status IDs are assigned per QMetry project and are NOT universal 37. - Using wrong status ID will update tests with incorrect status 38. - Example: ID 123268 might be 'Blocked' in one project but 'Passed' in another 39. - The allstatus array is the AUTHORITATIVE source for all status mappings 40. 41. HOW TO GET entityIDs (Test Case Run IDs): 42. 1. Call API 'Execution/Fetch Testcase Run ID' (FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN tool) 43. 2. From the response, get value of following attribute -> data[<index>].tcRunID 44. 3. Example: Single ID '66095087' or Multiple IDs '66095069,66095075,66095081' 45. 4. For bulk operations, provide comma-separated IDs without spaces 46. HOW TO GET qmTsRunId (Test Suite Run ID): 47. 1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE tool) 48. 2. From the response, get value of following attribute -> data[<index>].tsRunID 49. 3. Example: Test Suite Run ID might be '2720260' 50. HOW TO GET runStatusID (Execution Status ID) - DETAILED PROCESS: 51. 1. Call API 'Admin/Get info Service' (FETCH_PROJECT_INFO tool) with projectKey 52. 2. From the response, locate the 'allstatus' array 53. 3. Search for the status object where name matches your desired status (case-insensitive) 54. 4. Extract the 'id' property from the matching status object 55. 5. NEVER use example IDs from documentation - they are project-specific 56. 57. EXAMPLE allstatus ARRAY STRUCTURE: 58. allstatus: [ 59. { name: 'Passed', defaultName: 'passed', id: 123266, color: '#14892C|#FFFFFF' }, 60. { name: 'Failed', defaultName: 'failed', id: 123269, color: '#FF6666|#FFFFFF' }, 61. { name: 'Blocked', defaultName: 'blocked', id: 123268, color: '#CCCCCC|#FFFFFF' }, 62. { name: 'Not Run', defaultName: 'notrun', id: 123270, color: '#205081|#FFFFFF', isdefault: true }, 63. { name: 'Not Applicable', defaultName: 'empty', id: 123267, color: '#59AFE1|#FFFFFF' } 64. ] 65. Note: Above IDs are EXAMPLES ONLY - fetch actual IDs from your project 66. HOW TO GET dropID (Build/Drop ID) - OPTIONAL: 67. 1. Call API 'Build/List' (FETCH_BUILDS tool) 68. 2. From the response, get value of following attribute -> data[<index>].dropID 69. 3. Example: Build/Drop ID might be 947 70. ENTITY TYPES: 71. - 'TCR' = Test Case Run (most common use case) 72. - 'TCSR' = Test Case Step Run (for step-level execution updates) 73. BULK OPERATION FLAG: 74. - isBulkOperation=false: Single test case run update (one entityID) 75. - isBulkOperation=true: Multiple test case runs update (comma-separated entityIDs) 76. - Auto-detected: If entityIDs contains comma, defaults to true; otherwise false 77. AUTOMATION FLAG (isAutoExecuted) - OPTIONAL: 78. - '1' = Automated execution (test run by automation framework) 79. - '0' = Manual execution (test run by human tester) 80. - Used for execution tracking and reporting purposes 81. PART 11 COMPLIANCE (username & password) - CONDITIONAL: 82. - Required ONLY if Part 11 Compliance is active in your QMetry instance 83. - Used for regulatory compliance and audit trail purposes 84. - Not needed for standard QMetry installations 85. COMMENTS FIELD - OPTIONAL: 86. - Add execution notes, failure reasons, or status change context 87. - Useful for tracking why status was changed 88. - Appears in execution history and audit logs 89. COMMON EXECUTION STATUS NAMES: 90. - Pass: Test case executed successfully 91. - Fail: Test case failed with errors 92. - Blocked: Test case cannot be executed due to blockers 93. - Not Run: Test case not yet executed or needs re-execution 94. - WIP: Work In Progress - test case execution in progress 95. WORKFLOW FOR USER PROMPTS: 96. 1. If user says 'execute test case run by id to failed' or 'update status to fail': 97. - Fetch test case runs to get tcRunID (entityIDs) 98. - Fetch project info to get 'Fail' status ID (runStatusID) 99. - Set isBulkOperation=false for single ID 100. 2. If user says 'bulk update test case run status to pass' or 'update all to passed': 101. - Fetch test case runs to get multiple tcRunIDs 102. - Fetch project info to get 'Pass' status ID 103. - Set isBulkOperation=true 104. - Join multiple IDs with commas (no spaces) 105. 3. If user says 'execute status to not run of given test case run ids': 106. - Use provided IDs or fetch if needed 107. - Fetch project info to get 'Not Run' status ID 108. - Set isBulkOperation based on ID count 109. 4. If the user requests updating status for ALL executions of a test suite, the agent must: 110. 1. Call FETCH_EXECUTIONS_BY_TESTSUITE to get all qmTsRunIds. 111. 2. For each qmTsRunId: 112. - Call FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN to get tcRunID (entityIDs) 113. - Fetch project info to get 'Fail' status ID (runStatusID) 114. - Call BULK_UPDATE_EXECUTION_STATUS with the corresponding qmTsRunId + tcRunID + desired runStatusID 115. 3. Repeat until all executions are updated. 116. This tool is intended to be invoked multiple times in sequence for multi-execution updates. 117. FIELD MAPPING CRITICAL NOTES: 118. - entityIDs must be comma-separated STRING (e.g., '66095069,66095075') 119. - qmTsRunId must be STRING format (e.g., '2720260') 120. - runStatusID must be NUMERIC (e.g., 123268) 121. - dropID can be numeric or string (flexible) 122. API ENDPOINT: PUT /rest/execution/runstatus/bulkupdate 123. This tool is essential for test execution management and status tracking 124. Critical for maintaining accurate test execution records and reporting 125. Use for manual test execution updates and automated test result integration 126. Essential for test execution audit trails and compliance requirements
Input schema
Property Previous (0.42.0) Current (0.43.0) Change udfValuesByRunnot present object, additionalProperties {…}, propertyNames {…}optional - Added
viewIdnot present numberoptional - Added
14 unchanged entries
(schema root)commentsdropIDentityIDsentityTypeisAutoExecutedisBulkOperationpasswordprojectKeyqmRunObjqmTsRunIdrunStatusIDtypeusername
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_execute_quality_gate_reportModifiedWhat changed
- qmetry_execute_quality_gate_report — Schema change: input property added: extKeys.
- qmetry_execute_quality_gate_report: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousExecute a quality gate report by forwarding the request to the backend analytics engine and returning the results. **Toolset:** AI Agent **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - reportName (string) *required*: Report name identifier (e.g. 'RR' for Release Readiness). - gateIdentifier (string) *required*: Gate identifier to execute the report against (e.g. 'GATE1'). - projectId (number) *required*: Numeric project ID for the report scope. - releaseId (number): Optional release ID to scope the report to a specific release. - cycleIds (array): Optional array of cycle IDs to scope the report to specific cycles. - page (number): Optional page number for paginated report results. - limit (number): Maximum number of records to return per page. Defaults to 100 if not specified. (default: 100) **Use Cases:** 1. Generate a release readiness report for a specific project, release, and cycle 2. Execute a quality gate assessment to evaluate project health against gate criteria 3. Run a gate report scoped to specific cycles within a release 4. Produce analytics data for quality gate evaluation and decision-making **Examples:** 1. Execute a release readiness report for project 45851, release 90698, cycle 129140 ```json { "reportName": "RR", "gateIdentifier": "GATE1", "projectId": 45851, "releaseId": 90698, "cycleIds": [ 129140 ] } ``` Expected Output: { "data": [...], "total": 0, "success": true, "page": {} } 2. Execute a gate report without release/cycle scoping ```json { "reportName": "RR", "gateIdentifier": "GATE1", "projectId": 45851 } ``` Expected Output: { "data": [...], "total": 0, "success": true, "page": {} } **Hints:** 1. REQUIRED: 'reportName' identifies the report type (e.g. 'RR' for Release Readiness). 2. REQUIRED: 'gateIdentifier' identifies which gate to evaluate (e.g. 'GATE1'). 3. REQUIRED: 'projectId' must be a valid numeric project ID. 4. OPTIONAL: 'releaseId' scopes the report to a specific release. 5. OPTIONAL: 'cycleIds' scopes the report to specific test cycles within the release. 6. OPTIONAL: 'page' specifies the page number for paginated report results. 7. OPTIONAL: 'limit' sets the maximum number of records per page (defaults to 100). 8. Call 'Fetch Quality Gate Configuration' first to discover available gates and report parameters. 9. The response is returned exactly as received from the backend — no transformation is applied.
- CurrentExecute a quality gate report by forwarding the request to the backend analytics engine and returning the results. **Toolset:** AI Agent **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - reportName (string) *required*: Report name identifier (e.g. 'RR' for Release Readiness). - gateIdentifier (string) *required*: Gate identifier to execute the report against (e.g. 'GATE1'). - projectId (number) *required*: Numeric project ID for the report scope. - releaseId (number): Optional release ID to scope the report to a specific release. - cycleIds (array): Optional array of cycle IDs to scope the report to specific cycles. - extKeys (array): Optional array of external issue keys (e.g. Jira keys like 'PROJ-123') to scope the report to specific external requirements. - page (number): Optional page number for paginated report results. - limit (number): Maximum number of records to return per page. Defaults to 100 if not specified. (default: 100) **Use Cases:** 1. Generate a release readiness report for a specific project, release, and cycle 2. Execute a quality gate assessment to evaluate project health against gate criteria 3. Run a gate report scoped to specific cycles within a release 4. Run a gate report scoped to specific external (e.g. Jira) issue keys 5. Produce analytics data for quality gate evaluation and decision-making **Examples:** 1. Execute a release readiness report for project 45851, release 90698, cycle 129140 ```json { "reportName": "RR", "gateIdentifier": "GATE1", "projectId": 45851, "releaseId": 90698, "cycleIds": [ 129140 ] } ``` Expected Output: { "data": [...], "total": 0, "success": true, "page": {} } 2. Execute a gate report scoped to specific external issue keys ```json { "reportName": "RR", "gateIdentifier": "GATE1", "projectId": 45851, "releaseId": 90698, "extKeys": [ "PROJ-101", "PROJ-102" ] } ``` Expected Output: { "data": [...], "total": 0, "success": true, "page": {} } 3. Execute a gate report without release/cycle scoping ```json { "reportName": "RR", "gateIdentifier": "GATE1", "projectId": 45851 } ``` Expected Output: { "data": [...], "total": 0, "success": true, "page": {} } **Hints:** 1. REQUIRED: 'reportName' identifies the report type (e.g. 'RR' for Release Readiness). 2. REQUIRED: 'gateIdentifier' identifies which gate to evaluate (e.g. 'GATE1'). 3. REQUIRED: 'projectId' must be a valid numeric project ID. 4. OPTIONAL: 'releaseId' scopes the report to a specific release. 5. OPTIONAL: 'cycleIds' scopes the report to specific test cycles within the release. 6. OPTIONAL: 'extKeys' scopes the report to specific external issue keys (e.g. Jira keys like 'PROJ-123'). 7. OPTIONAL: 'page' specifies the page number for paginated report results. 8. OPTIONAL: 'limit' sets the maximum number of records per page (defaults to 100). 9. Call 'Fetch Quality Gate Configuration' first to discover available gates and report parameters. 10. The response is returned exactly as received from the backend — no transformation is applied.
Input schema
Property Previous (0.42.0) Current (0.43.0) Change extKeysnot present arrayoptional - Added
extKeys › [items]not present string - Added
10 unchanged entries
(schema root)cycleIdscycleIds › [items]gateIdentifierlimitpageprojectIdprojectKeyreleaseIdreportName
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_fetch_api_call_quotaAddedWhat changed
- New read-only tool qmetry_fetch_api_call_quota.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.42.0) Current (0.43.0) Change (schema root)not present object - Added
projectKeynot present string, default="default"optional - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_fetch_executions_by_test_suiteModifiedWhat changed
- qmetry_fetch_executions_by_test_suite: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet executions for a given test suite in QMetry **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tsID (number) *required*: Test Suite numeric ID. CRITICAL: the parameter name is 'tsID' — do NOT use 'testSuiteId', 'testSuiteID', 'suiteId', or other variants. Accepts a string or number. NOTE: To get the tsID - Call API 'Testsuite/Fetch Testsuite' From the response, get value of following attribute -> data[<index>].id - tsFolderID (number): Test Suite folder ID. CRITICAL: the parameter name is 'tsFolderID' — do NOT use 'testSuiteFolderId', 'folderId', 'folderID', or other variants. Accepts a string or number. Get from project info response → rootFolders.TS.id. Use FETCH_PROJECT_INFO tool first if not provided by user. - gridName (string): Grid Name to be displayed (default 'TESTEXECUTIONLIST') - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") **Output Description:** JSON object with executions array containing execution details, status, platforms, releases, and execution metadata **Use Cases:** 1. Get all executions for a specific test suite for reporting purposes 2. Analyze test execution results and trends within a test suite 3. Filter executions by release, cycle, platform, or automation status 4. Monitor test suite execution performance across different environments 5. Generate execution reports for specific test suites 6. Track execution history and patterns for test suite optimization 7. Validate test suite execution coverage across releases and cycles 8. Audit test execution data for compliance and quality assurance 9. Export execution data for external reporting and analytics **Examples:** 1. Get all executions for test suite ID 194955 ```json { "tsID": 194955 } ``` Expected Output: List of executions for the test suite with execution details, status, and metadata 2. Get executions with test suite folder and view ID ```json { "tsID": 194955, "tsFolderID": 126554, "viewId": 41799 } ``` Expected Output: Executions filtered by test suite folder and specific view configuration 3. Filter executions by release and cycle ```json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"releaseID\"},{\"type\":\"list\",\"value\":[111577],\"field\":\"cycleID\"}]" } ``` Expected Output: Executions filtered by specific release (55178) and cycle (111577) 4. Filter executions by platform and automation status ```json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[12345],\"field\":\"platformID\"},{\"type\":\"boolean\",\"value\":true,\"field\":\"isAutomatedFlag\"}]" } ``` Expected Output: Automated executions filtered by specific platform (12345) 5. Get only active (non-archived) executions ```json { "tsID": 194955, "filter": "[{\"value\":[0],\"type\":\"list\",\"field\":\"isArchived\"}]" } ``` Expected Output: Active executions that are not archived 6. Get executions with custom pagination and grid name ```json { "tsID": 194955, "gridName": "TESTEXECUTIONLIST", "page": 1, "limit": 25 } ``` Expected Output: Paginated list of executions with 25 items per page using specific grid configuration **Hints:** 1. !MOST IMPORTANT HOW TO GET viewId: 2. CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool. 3. The viewId parameter must be fetched from the active project's info (latestViews.TEL.viewId). 4. Each QMetry project may have a different test execution list viewId, so using a stale or incorrect viewId will result in incomplete or invalid executions list data by test suite id. 5. Usage workflow: 6. 1. Fetch project info for the current project (Admin/Get info Service). 7. 2. Extract latestViews.TEL.viewId from the response. 8. 3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call. 9. Example: 10. { 11. tsID: 1533730, 12. viewId: 94194, 13. gridName: 'TESTEXECUTIONLIST' 14. } 15. CRITICAL: tsID parameter is REQUIRED - this is the Test Suite numeric ID 16. HOW TO GET tsID: 17. 1. Call API 'Testsuite/Fetch Testsuite' to get available test suites 18. 2. From the response, get value of following attribute -> data[<index>].id 19. 3. Example: Test Suite 'Regression Suite' might have ID 194955 20. HOW TO GET tsFolderID (optional): 21. 1. Call API 'Testsuite/List of folders' to get test suite folders 22. 2. From the response, get value of following attribute -> data[<index>].id 23. 3. Example: Test Suite folder might have ID 126554 24. FILTER CAPABILITIES: Extensive filtering by execution properties 25. FILTER FIELDS: releaseID (list), cycleID (list), platformID (list), isAutomatedFlag (boolean), isArchived (list) 26. RELEASE/CYCLE FILTERING: Use numeric IDs in list format (get from FETCH_RELEASES_AND_CYCLES) 27. PLATFORM FILTERING: Use numeric platform IDs (get from FETCH_PLATFORMS) 28. AUTOMATION STATUS: Use boolean true/false for isAutomatedFlag field 29. ARCHIVE STATUS: 0=Active executions, 1=Archived executions 30. GRID NAME: Default is 'TESTEXECUTIONLIST' - used for execution list display configuration 31. VIEW ID: Optional numeric identifier for specific execution view configurations 32. Multiple filter conditions are combined with AND logic 33. Use pagination for large execution result sets (start, page, limit parameters) 34. This tool is essential for test execution analysis and reporting 35. Critical for monitoring test suite performance and execution trends 36. Use for compliance reporting and execution audit trails 37. Essential for test execution planning and resource optimization
- CurrentGet executions for a given test suite in QMetry **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tsID (number) *required*: Test Suite numeric ID. CRITICAL: the parameter name is 'tsID' — do NOT use 'testSuiteId', 'testSuiteID', 'suiteId', or other variants. Accepts a string or number. NOTE: To get the tsID - Call API 'Testsuite/Fetch Testsuite' From the response, get value of following attribute -> data[<index>].id - tsFolderID (number): Test Suite folder ID. CRITICAL: the parameter name is 'tsFolderID' — do NOT use 'testSuiteFolderId', 'folderId', 'folderID', or other variants. Accepts a string or number. Get from project info response → rootFolders.TS.id. Use FETCH_PROJECT_INFO tool first if not provided by user. - gridName (string): Grid Name to be displayed (default 'TESTEXECUTIONLIST') - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") **Output Description:** JSON object with executions array containing execution details, status, platforms, releases, and execution metadata. Each execution entry may include 'linkedDfCount' (defects linked to the test execution) and 'linkedStepDfCount' (defects linked to the test step executions) - report both when linked defects are asked about. **Use Cases:** 1. Get all executions for a specific test suite for reporting purposes 2. Analyze test execution results and trends within a test suite 3. Filter executions by release, cycle, platform, or automation status 4. Monitor test suite execution performance across different environments 5. Generate execution reports for specific test suites 6. Track execution history and patterns for test suite optimization 7. Validate test suite execution coverage across releases and cycles 8. Audit test execution data for compliance and quality assurance 9. Export execution data for external reporting and analytics **Examples:** 1. Get all executions for test suite ID 194955 ```json { "tsID": 194955 } ``` Expected Output: List of executions for the test suite with execution details, status, and metadata 2. Get executions with test suite folder and view ID ```json { "tsID": 194955, "tsFolderID": 126554, "viewId": 41799 } ``` Expected Output: Executions filtered by test suite folder and specific view configuration 3. Filter executions by release and cycle ```json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"releaseID\"},{\"type\":\"list\",\"value\":[111577],\"field\":\"cycleID\"}]" } ``` Expected Output: Executions filtered by specific release (55178) and cycle (111577) 4. Filter executions by platform and automation status ```json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[12345],\"field\":\"platformID\"},{\"type\":\"boolean\",\"value\":true,\"field\":\"isAutomatedFlag\"}]" } ``` Expected Output: Automated executions filtered by specific platform (12345) 5. Get only active (non-archived) executions ```json { "tsID": 194955, "filter": "[{\"value\":[0],\"type\":\"list\",\"field\":\"isArchived\"}]" } ``` Expected Output: Active executions that are not archived 6. Get executions with custom pagination and grid name ```json { "tsID": 194955, "gridName": "TESTEXECUTIONLIST", "page": 1, "limit": 25 } ``` Expected Output: Paginated list of executions with 25 items per page using specific grid configuration **Hints:** 1. !MOST IMPORTANT HOW TO GET viewId: 2. CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool. 3. The viewId parameter must be fetched from the active project's info (latestViews.TEL.viewId). 4. Each QMetry project may have a different test execution list viewId, so using a stale or incorrect viewId will result in incomplete or invalid executions list data by test suite id. 5. Usage workflow: 6. 1. Fetch project info for the current project (Admin/Get info Service). 7. 2. Extract latestViews.TEL.viewId from the response. 8. 3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call. 9. Example: 10. { 11. tsID: 1533730, 12. viewId: 94194, 13. gridName: 'TESTEXECUTIONLIST' 14. } 15. CRITICAL: tsID parameter is REQUIRED - this is the Test Suite numeric ID 16. HOW TO GET tsID: 17. 1. Call API 'Testsuite/Fetch Testsuite' to get available test suites 18. 2. From the response, get value of following attribute -> data[<index>].id 19. 3. Example: Test Suite 'Regression Suite' might have ID 194955 20. HOW TO GET tsFolderID (optional): 21. 1. Call API 'Testsuite/List of folders' to get test suite folders 22. 2. From the response, get value of following attribute -> data[<index>].id 23. 3. Example: Test Suite folder might have ID 126554 24. FILTER CAPABILITIES: Extensive filtering by execution properties 25. FILTER FIELDS: releaseID (list), cycleID (list), platformID (list), isAutomatedFlag (boolean), isArchived (list) 26. RELEASE/CYCLE FILTERING: Use numeric IDs in list format (get from FETCH_RELEASES_AND_CYCLES) 27. PLATFORM FILTERING: Use numeric platform IDs (get from FETCH_PLATFORMS) 28. AUTOMATION STATUS: Use boolean true/false for isAutomatedFlag field 29. ARCHIVE STATUS: 0=Active executions, 1=Archived executions 30. GRID NAME: Default is 'TESTEXECUTIONLIST' - used for execution list display configuration 31. VIEW ID: Optional numeric identifier for specific execution view configurations 32. Multiple filter conditions are combined with AND logic 33. Use pagination for large execution result sets (start, page, limit parameters) 34. This tool is essential for test execution analysis and reporting 35. Critical for monitoring test suite performance and execution trends 36. Use for compliance reporting and execution audit trails 37. Essential for test execution planning and resource optimization 38. LINKED DEFECTS/ISSUES: Each execution record can expose TWO separate defect counts - 'linkedDfCount' is the count of defects/issues linked to the TEST EXECUTION itself, and 'linkedStepDfCount' is the count of defects/issues linked to that execution's TEST STEP executions. Whenever asked about linked defects/issues for an execution, report BOTH counts (linkedDfCount and linkedStepDfCount) - do not report only one.
Input schema
Input schema unchanged.
10 unchanged entries
(schema root)filtergridNamelimitpageprojectKeystarttsFolderIDtsIDviewId
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_fetch_test_case_runs_by_test_suite_runModifiedWhat changed
- qmetry_fetch_test_case_runs_by_test_suite_run: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet test case runs under a specific test suite run execution in QMetry, including Test Run UDF values. ALWAYS present results as a unified table: Test Case Key | Test Case Summary | Executed Version | Execution Status | <UDF Label columns…>. NEVER show a separate type+value breakdown — always combine identification fields and UDF values in one table per run. **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tsrunID (string) *required*: Test Suite Run ID. CRITICAL: the parameter name is 'tsrunID' — do NOT use 'testSuiteRunId', 'tsRunID', 'testSuiteRunID', or any other variant. Accepts a string or number (e.g. 731600 or '731600' — both are valid). To get this value: Call 'Fetch Executions by Test Suite' → use data[<index>].tsRunID from the response. - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") - udfFilter (string): User-defined field filter as JSON string (default '[]') (default: "[]") - tcrUdfFilter (string): Test Case Run (TCR) UDF filter as JSON string (default '[]'). Used to filter test case runs by Test Run UDF field values. Format: '[{"type":"list","value":[<listItemId1>,<listItemId2>],"field":"<udfFieldKey>"}]'. Example: '[{"type":"list","value":[5108701,5108697],"field":"8260LUP"}]' filters runs where the UDF field '8260LUP' has those list item IDs. (default: "[]") - showTcWithDefects (boolean): Show test case runs with linked defects (default: false) **Output Description:** JSON object with test case runs array. Each row ALWAYS contains these mandatory identification fields: 'entityKey' (Test Case Key, e.g. 'MAC-TC-123'), 'summary' (Test Case Summary/name), 'latestVersion' (Executed Version, e.g. 'v1', 'v2'), 'runStatus' (Execution Status label, e.g. 'Passed', 'Failed', 'Not Run'), 'runStatusID' (numeric status ID), 'tcRunID' (numeric Test Run ID), and 'testRunUdfs' (object with Test Run UDF field keys mapped to their values, parsed from the raw 'udfjson' field; HTML stripped from rich text). UDF values can also be fetched in enriched form via FETCH_TEST_RUN_UDF_VALUES or field metadata via FETCH_TEST_RUN_UDF_METADATA. The top-level response includes 'hasTcRunUdf' (boolean), 'total' (count), and pagination metadata. **Use Cases:** 1. Get all test case runs under a specific test suite run execution 2. Fetch Test Run UDF values for all test case executions in a test suite run — always show Test Case Key, Summary, and Execution Status alongside UDFs 3. Fetch Test Run UDF values for a specific test case execution by tcRunID 4. Filter test case runs by Test Run UDF field values (e.g. show only runs where dropdown UDF = specific option) 5. Analyze individual test case execution results, status, and custom UDF metadata 6. Monitor test case run performance and execution trends 7. Generate detailed test execution reports including custom UDF data 8. Track test case run history and execution patterns 9. Validate test case run coverage and execution completeness 10. Audit test case run data with UDF values for compliance and quality assurance 11. Export detailed test case run data including Test Run UDFs for external reporting 12. Retrieve paginated test case run results for large test suite executions **Examples:** 1. Get all test case runs for test suite run ID '107021' ```json { "tsrunID": "107021", "viewId": 6887 } ``` Expected Output: Present as ONE unified table — never as a separate type+value breakdown. Example: | Test Case Key | Test Case Summary | Executed Version | Execution Status | Tested By | Environments UDF | Execution Type | Country | | MAC-TC-5 | Login - valid credential | v1 | Passed | varis | chrome, edge, safari | Functional | India > i3 | | MAC-TC-6 | Login - invalid password | v2 | Failed | john | firefox | Regression | - | Columns: Test Case Key (entityKey) | Test Case Summary (summary) | Executed Version (latestVersion) | Execution Status (runStatus) | then one column per UDF label. Use the UDF 'label' as column header. Show null UDF values as '-'. 2. Fetch Test Run UDF values for all executions in test suite run '728995' ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20 } ``` Expected Output: Present as ONE unified table combining identification fields and UDF values — never a separate type+value breakdown. Example: | Test Case Key | Test Case Summary | Executed Version | Execution Status | Tested By | Environments UDF | Planned Execution Date | Execution Type | | MAC-TC-5 | Login test | v1 | Passed | varis | chrome, edge, safari | - | Functional | HTML is stripped from LARGETEXT UDF fields. Null values shown as '-'. 3. Filter by Test Run UDF list/dropdown field (single-select or multi-select lookup) — runs where UDF '8260LUP' has list item IDs 5108701 or 5108697 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"}]" } ``` Expected Output: Filtered test case runs matching the lookup list UDF values 4. Filter by Test Run UDF multi-lookup list field — runs where multi-select UDF 'PGTE_MULTILOOKUPLIST' contains list item IDs 5126503 or 5126502 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5126503,5126502],\"field\":\"PGTE_MULTILOOKUPLIST\"}]" } ``` Expected Output: Filtered test case runs where multi-lookup UDF matches any of the given list item IDs 5. Filter by Test Run UDF cascading dropdown field — runs where cascading UDF 'cascade_vK' has list item IDs 5126498 or 5126499 (must set isCascading:true) ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5126498,5126499],\"field\":\"cascade_vK\",\"isCascading\":true}]" } ``` Expected Output: Filtered test case runs matching the cascading dropdown UDF values 6. Filter by Test Run UDF short text field — runs where text UDF 'TRString' contains the value 'str' ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"}]" } ``` Expected Output: Filtered test case runs where short text UDF matches the search string 7. Filter by Test Run UDF large text field — runs where large text UDF 'vk_large_text' contains 'this is large text' ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"string\",\"field\":\"vk_large_text\",\"value\":\"this is large text\"}]" } ``` Expected Output: Filtered test case runs where large text UDF matches the search string 8. Filter by Test Run UDF date field — runs where date UDF 'PGTE_DATEPICKER' is after a specific date (comparison: gt) and before another date (comparison: lt) ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"gt\",\"value\":\"06-01-2026\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"lt\",\"value\":\"06-30-2026\"}]" } ``` Expected Output: Filtered test case runs where date UDF falls within the specified range 9. Filter by Test Run UDF numeric field — runs where numeric UDF 'NB_number_TR' equals 2 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]" } ``` Expected Output: Filtered test case runs where numeric UDF equals the specified value 10. Combine multiple Test Run UDF filters — filter by list UDF AND string UDF AND numeric UDF simultaneously ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"},{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"},{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]" } ``` Expected Output: Test case runs matching ALL specified UDF filter conditions (AND logic) 11. Full filter combination — standard field filter + Test Run UDF filter + show only runs with defects ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20, "filter": "[]", "udfFilter": "[]", "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"},{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"},{\"type\":\"string\",\"field\":\"vk_large_text\",\"value\":\"this is large text\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"gt\",\"value\":\"\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"lt\",\"value\":\"\"},{\"type\":\"list\",\"value\":[5126503,5126502],\"field\":\"PGTE_MULTILOOKUPLIST\"},{\"type\":\"list\",\"value\":[5126498,5126499],\"field\":\"cascade_vK\",\"isCascading\":true},{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]", "showTcWithDefects": false } ``` Expected Output: Test case runs filtered by all 7 UDF field type conditions simultaneously 12. Get paginated test case runs with standard runStatus filter ```json { "tsrunID": "2362144", "viewId": 104123, "start": 0, "page": 1, "limit": 25, "filter": "[{\"type\":\"string\",\"value\":\"Failed\",\"field\":\"runStatus\"}]" } ``` Expected Output: Paginated list of Failed test case runs with 25 items per page including testRunUdfs 13. Show only test case runs with linked defects, filtered by Test Run UDF list value ```json { "tsrunID": "107021", "viewId": 6887, "showTcWithDefects": true, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701],\"field\":\"8260LUP\"}]" } ``` Expected Output: Test case runs with defects where the specified Test Run UDF matches **Hints:** 1. === MANDATORY RESPONSE FORMAT — READ THIS BEFORE RENDERING ANY OUTPUT === 2. 3. PIVOT RULE — CRITICAL: 4. The 'testRunUdfs' field on each row is a key-value map (object) of UDF field keys to their values. 5. You MUST pivot this into TABLE COLUMNS — do NOT render it as rows. 6. → Each key in testRunUdfs = use the UDF human-readable label as the column header 7. → Each value in testRunUdfs = the cell value for that run's row 8. → 'fieldType' / 'fieldID' = INTERNAL METADATA — NEVER show these as columns 9. 10. FORBIDDEN PATTERNS — NEVER do any of these: 11. ❌ Do NOT render a separate sub-table (Label | Type | Value) per tcRunID 12. ❌ Do NOT show 'Type' or 'fieldType' as a visible column 13. ❌ Do NOT group output by tcRunID with individual breakdowns beneath each 14. ❌ Do NOT show raw UDF field keys (e.g. 'TRString', '8260LUP') as column headers — use human-readable labels 15. 16. REQUIRED OUTPUT — ONE unified table, all runs as rows: 17. | Test Case Key | Test Case Summary | Executed Version | Execution Status | <UDF Label 1> | <UDF Label 2> | ... | 18. |---------------|-------------------|------------------|------------------|---------------|---------------|-----| 19. | VKMCP-TC-1 | Login test | v1 | Not Run | varis | chrome, edge | ... | 20. | VKMCP-TC-2 | Invalid password | v2 | Not Run | john | firefox | ... | 21. 22. MANDATORY COLUMNS (always first, in this order): 23. 1. Test Case Key → entityKey (e.g. 'VKMCP-TC-1') 24. 2. Test Case Summary → summary (test case name) 25. 3. Executed Version → latestVersion (e.g. 'v1', 'v2') 26. 4. Execution Status → runStatus (e.g. 'Not Run', 'Passed', 'Failed') 27. 5. Tested By → testedBy/executedBy when present 28. 6+. One column per UDF field — use the human-readable label as header, the value as the cell. 29. 30. Null UDF values → show as '-' in the cell. 31. If testRunUdfs is empty or hasTcRunUdf is false, still show columns 1-5. 32. CHAINING WITH FETCH TEST RUN UDF VALUES: 33. If the user explicitly asks for Test Run UDFs with these test case runs, call 'Fetch Test Run UDF Values' after this tool with sourceContext='testSuiteRun' and sourceRows=<this response data>. Render that tool's unifiedTableRows as the final answer. 34. === END MANDATORY RESPONSE FORMAT === 35. 36. CRITICAL WORKFLOW FOR FETCHING ALL EXECUTIONS OF A TEST SUITE: 37. When user asks to: 38. - 'fetch all executions' 39. - 'get all test runs' 40. - 'fetch all tcRunIDs for test suite X' 41. - 'update status for all executions of test suite X' 42. STEP 1: First call FETCH_EXECUTIONS_BY_TESTSUITE tool with the test suite ID (tsID, not entityKey) 43. - This returns ALL execution records for that test suite (could be 3, 5, 9, or any number) 44. - Extract ALL tsRunID values from the response data array 45. - Example response: data: [{tsRunID: '2739237', ...}, {tsRunID: '2739236', ...}, {tsRunID: '2739235', ...}] 46. STEP 2: For EACH tsRunID from Step 1, call this tool (FETCH_TEST_CASE_RUNS_BY_TESTSUITE_RUN) 47. - This returns all test case runs (tcRunID values) for that specific execution 48. - Repeat for ALL tsRunID values discovered in Step 1 49. STEP 3: Collect all tcRunID values from all executions 50. - Now you have the complete list of test case runs across ALL executions 51. - Use these for bulk status updates or other operations 52. CRITICAL ERROR TO AVOID: 53. - NEVER assume or hard-code only 2-3 execution IDs 54. - NEVER skip Step 1 - always discover ALL executions first 55. - NEVER fetch tcRunIDs for only some executions - get ALL of them 56. - If there are 9 executions, you must fetch tcRunIDs for all 9, not just 2 57. EXAMPLE WORKFLOW: 58. User: 'Fetch all test case runs for test suite VKMCP-TS-21' 59. Step 1: Call FETCH_EXECUTIONS_BY_TESTSUITE with tsID (resolved from VKMCP-TS-21) 60. Result: Found 9 executions with tsRunIDs: 2739237, 2739236, 2739235, 2739234, 2739233, 2739232, 2739231, 2739230, 2739229 61. Step 2: Call this tool 9 times (once for each tsRunID) 62. Call 1: tsrunID='2739237' -> returns 54 tcRunIDs 63. Call 2: tsrunID='2739236' -> returns 54 tcRunIDs 64. ... (repeat for all 9) 65. Step 3: Total collected: 9 executions × 54 test cases = 486 total tcRunIDs 66. 67. PERFORMANCE CONSIDERATIONS FOR LARGE TEST RUNS: 68. When dealing with large numbers of test case runs (500+, 1000+), follow these guidelines: 69. 1. ALWAYS inform the user about the scale BEFORE starting operations: 70. Example: 'Found 9 executions with approximately 486 test case runs. This will require fetching data from all 9 executions and may take a moment.' 71. 2. For bulk status updates on 1000+ test case runs: 72. - NEVER attempt to update all 1000+ in a single operation 73. - Break into smaller batches of 10-20 test case runs per update 74. - Inform user: 'Found 1000 test case runs. Will process in batches of 20 to ensure reliability and performance.' 75. - Show progress: 'Processing batch 1/50 (20 test runs)...', 'Batch 2/50...' 76. 3. Recommended batch sizes: 77. - For status updates: 10-20 test case runs per batch 78. - For fetching data: Can handle larger batches (50-100) 79. - Adjust based on API response times and timeout limits 80. 4. Always provide progress updates for long-running operations: 81. - Before: 'Processing 1000 test runs in 50 batches of 20...' 82. - During: 'Completed 200/1000 test runs (10 batches)...' 83. - After: 'Successfully updated all 1000 test case runs.' 84. 5. Error handling for batch operations: 85. - If a batch fails, report which batch and continue with remaining 86. - Provide summary at the end: 'Completed 48/50 batches. 2 batches failed (batch 23, 45).' 87. - Allow user to retry failed batches specifically 88. EXAMPLE LARGE-SCALE WORKFLOW: 89. User: 'Update status to Failed for all test runs in VKMCP-TS-21' 90. Step 1: Discover all executions (9 found) 91. Step 2: Fetch all tcRunIDs (486 total) 92. Step 3: Inform user: 'Found 486 test case runs across 9 executions. Will update in 25 batches of 20 runs each.' 93. Step 4: Process in batches with progress updates 94. Step 5: Report completion: 'Successfully updated all 486 test case runs to Failed status.' 95. 96. CRITICAL: tsrunID and viewId parameters are REQUIRED 97. tsrunID is a STRING identifier for the test suite run execution 98. viewId is a NUMERIC identifier for the test execution view 99. !MOST IMPORTANT HOW TO GET tsrunID: 100. 1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE) to get ALL available executions 101. 2. From the response, get value of following attribute -> data[<index>].tsRunID for EVERY execution 102. 3. Example: Test Suite might have multiple executions with IDs '107021', '107022', '107023', etc. 103. 4. NEVER assume there are only 2-3 executions - always fetch to discover the actual count 104. !MOST IMPORTANT HOW TO GET viewId: 105. CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool. 106. The viewId parameter must be fetched from the active project's info (latestViews.TE.viewId). 107. Each QMetry project may have a different test execution viewId, so using a stale or incorrect viewId will result in incomplete or invalid test case run data. 108. Usage workflow: 109. 1. Fetch project info for the current project (Admin/Get info Service). 110. 2. Extract latestViews.TE.viewId from the response. 111. 3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call. 112. Example: 113. { 114. tsrunID: "2362144", 115. viewId: 104123, 116. start: 0, 117. page: 1, 118. limit: 25 119. } 120. This ensures the tool fetches the proper execution runs data for the selected project context. 121. SUPPORTED PARAMETERS: start, page, limit, tsrunID, viewId, filter, udfFilter, tcrUdfFilter, showTcWithDefects 122. PAGINATION: Use start, page, and limit for result pagination 123. PAYLOAD FORMAT: {"start": 0, "page": 1, "limit": 10, "tsrunID": "2362144", "viewId": 104123} 124. 125. === TEST RUN UDF (tcrUdfFilter) — ALL 7 FIELD TYPE FORMATS === 126. tcrUdfFilter filters test case RUNS by Test Run UDF values (not test case UDFs — use udfFilter for those). 127. Value is a JSON array string. Multiple conditions are combined with AND logic. 128. Base structure: {"type":"<fieldType>", "field":"<udfFieldKey>", "value":<value> [,"comparison":"..."] [,"isCascading":true]} 129. 130. --- TYPE 1: list (single-select lookup / dropdown) --- 131. Use for: single-select lookup list UDF fields (one value selected from a list). 132. value: array of numeric list item IDs — get IDs from FETCH_CUSTOM_LIST_ITEMS tool. 133. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>]} 134. Example: [{"type":"list","value":[5108701,5108697],"field":"8260LUP"}] 135. Matches runs where the UDF value is ANY of the provided list item IDs (OR within the array). 136. 137. --- TYPE 2: list (multi-select lookup list) --- 138. Use for: multi-select lookup list UDF fields (multiple values can be selected). 139. Syntax identical to single-select list — same format, just the UDF field itself is multi-select. 140. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>]} 141. Example: [{"type":"list","value":[5126503,5126502],"field":"PGTE_MULTILOOKUPLIST"}] 142. Matches runs where ANY of the UDF's selected values match any of the provided IDs. 143. 144. --- TYPE 3: list (cascading dropdown) --- 145. Use for: cascading dropdown UDF fields (parent-child linked dropdowns). MUST add isCascading:true. 146. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>], "isCascading":true} 147. Example: [{"type":"list","value":[5126498,5126499],"field":"cascade_vK","isCascading":true}] 148. CRITICAL: missing isCascading:true on a cascading field will cause incorrect results or API error. 149. 150. --- TYPE 4: string (short text) --- 151. Use for: single-line text UDF fields. 152. value: the string to search for (partial match / contains). 153. Format: {"type":"string", "field":"<fieldKey>", "value":"<searchText>"} 154. Example: [{"type":"string","field":"TRString","value":"str"}] 155. 156. --- TYPE 5: string (large text / rich text) --- 157. Use for: multi-line or rich text UDF fields. Syntax is identical to short text string type. 158. Format: {"type":"string", "field":"<fieldKey>", "value":"<searchText>"} 159. Example: [{"type":"string","field":"vk_large_text","value":"this is large text"}] 160. NOTE: Search is against the raw (HTML) content stored in the field; plain text search terms work fine. 161. 162. --- TYPE 6: date --- 163. Use for: date picker UDF fields. REQUIRES a 'comparison' property. 164. comparison: 'gt' = after the date (greater than), 'lt' = before the date (less than). 165. value: date string in 'MM-DD-YYYY' format, or empty string '' to leave the bound open. 166. Format: {"type":"date", "field":"<fieldKey>", "comparison":"gt"|"lt", "value":"MM-DD-YYYY"} 167. Example — date range: [{"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"},{"type":"date","field":"PGTE_DATEPICKER","comparison":"lt","value":"06-30-2026"}] 168. Example — open-ended (no upper bound): [{"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"}] 169. To filter by a single date use two conditions (gt day-before AND lt day-after) or just one bound. 170. CRITICAL: 'comparison' field is mandatory for date type — omitting it causes API error. 171. 172. --- TYPE 7: numeric --- 173. Use for: number UDF fields. 174. value: a number (integer or decimal). 175. Format: {"type":"numeric", "field":"<fieldKey>", "value":<number>} 176. Example: [{"type":"numeric","value":2,"field":"NB_number_TR"}] 177. 178. --- COMBINING MULTIPLE FILTERS --- 179. All conditions in tcrUdfFilter array use AND logic — runs must satisfy ALL conditions. 180. Full example (all 7 types combined): 181. [ 182. {"type":"list","value":[5108701,5108697],"field":"8260LUP"}, 183. {"type":"list","value":[5126503,5126502],"field":"PGTE_MULTILOOKUPLIST"}, 184. {"type":"list","value":[5126498,5126499],"field":"cascade_vK","isCascading":true}, 185. {"type":"string","field":"TRString","value":"str"}, 186. {"type":"string","field":"vk_large_text","value":"large text"}, 187. {"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"}, 188. {"type":"date","field":"PGTE_DATEPICKER","comparison":"lt","value":"06-30-2026"}, 189. {"type":"numeric","value":2,"field":"NB_number_TR"} 190. ] 191. --- FILTER PARAMETER SUMMARY --- 192. tcrUdfFilter: filter by Test Run UDF fields (this section) 193. udfFilter: filter by Test Case UDF fields (different from test run UDFs) 194. filter: filter by standard execution fields (runStatus, executedBy, etc.) 195. All three can be combined in a single request — they are independently applied with AND logic. 196. 197. hasTcRunUdf FLAG — IMPORTANT: 198. The response contains a 'hasTcRunUdf' boolean flag at the top level. 199. hasTcRunUdf: true → Project has Test Run UDFs configured; each record includes 'testRunUdfs' object. 200. hasTcRunUdf: false → Project has NO Test Run UDFs configured. 201. When hasTcRunUdf is false, the response includes a 'testRunUdfNote' with a professional explanation. 202. Inform the user: 'No Test Run UDFs are configured for this project. Contact a project administrator to set up Test Run UDF fields.' 203. NEVER attempt to read testRunUdfs from records when hasTcRunUdf is false — the field will not be present. 204. 205. TEST RUN UDF RESPONSE (testRunUdfs): 206. When the API returns Test Run UDF data, each row will include a 'testRunUdfs' object. 207. This is a key-value map of UDF field keys to their values, parsed from the API's 'udfjson' field. 208. HTML is stripped from rich text (large text) UDF fields for readable LLM output. 209. Example testRunUdfs in response: 210. testRunUdfs: { 211. "8260LUP": "l1", 212. "look_554": "99", 213. "cascade_vK": {"child": "aa", "parent": "abc"}, 214. "dateNJ": "06-02-2026", 215. "NB_Multilppup_TR": ["ahd"], 216. "Jal_Largetext": "asdef asdfads asdfasf asdf asdf asfd a sdfa" 217. } 218. Use pagination for large result sets (start, page, limit parameters) 219. This tool is essential for detailed test execution analysis and reporting 220. Critical for monitoring individual test case execution performance and UDF values 221. Use for compliance reporting and execution audit trails 222. Essential for test execution quality assurance and trend analysis
- CurrentGet test case runs under a specific test suite run execution in QMetry, including Test Run UDF values. ALWAYS present results as a unified table: Test Case Key | Test Case Summary | Executed Version | Execution Status | Linked Defects (Execution) | Linked Defects (Steps) | <UDF Label columns…>. NEVER show a separate type+value breakdown — always combine identification fields and UDF values in one table per run. Linked defects are TWO separate counts, never combine them into one 'Issues Linked' column. **Toolset:** Test Suites **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tsrunID (string) *required*: Test Suite Run ID. CRITICAL: the parameter name is 'tsrunID' — do NOT use 'testSuiteRunId', 'tsRunID', 'testSuiteRunID', or any other variant. Accepts a string or number (e.g. 731600 or '731600' — both are valid). To get this value: Call 'Fetch Executions by Test Suite' → use data[<index>].tsRunID from the response. - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") - udfFilter (string): User-defined field filter as JSON string (default '[]') (default: "[]") - tcrUdfFilter (string): Test Case Run (TCR) UDF filter as JSON string (default '[]'). Used to filter test case runs by Test Run UDF field values. Format: '[{"type":"list","value":[<listItemId1>,<listItemId2>],"field":"<udfFieldKey>"}]'. Example: '[{"type":"list","value":[5108701,5108697],"field":"8260LUP"}]' filters runs where the UDF field '8260LUP' has those list item IDs. (default: "[]") - showTcWithDefects (boolean): Show test case runs with linked defects (default: false) **Output Description:** JSON object with test case runs array. Each row ALWAYS contains these mandatory identification fields: 'entityKey' (Test Case Key, e.g. 'MAC-TC-123'), 'summary' (Test Case Summary/name), 'latestVersion' (Executed Version, e.g. 'v1', 'v2'), 'runStatus' (Execution Status label, e.g. 'Passed', 'Failed', 'Not Run'), 'runStatusID' (numeric status ID), 'tcRunID' (numeric Test Run ID), 'linkedDfCount' (defects/issues linked to the test case run itself) and 'linkedStepDfCount' (defects/issues linked to that run's test step executions) — these are TWO SEPARATE counts and must always be reported separately when linked defects are asked about, and 'testRunUdfs' (object with Test Run UDF field keys mapped to their values, parsed from the raw 'udfjson' field; HTML stripped from rich text). UDF values can also be fetched in enriched form via FETCH_TEST_RUN_UDF_VALUES or field metadata via FETCH_TEST_RUN_UDF_METADATA. The top-level response includes 'hasTcRunUdf' (boolean), 'total' (count), and pagination metadata. **Use Cases:** 1. Get all test case runs under a specific test suite run execution 2. Fetch Test Run UDF values for all test case executions in a test suite run — always show Test Case Key, Summary, and Execution Status alongside UDFs 3. Fetch Test Run UDF values for a specific test case execution by tcRunID 4. Filter test case runs by Test Run UDF field values (e.g. show only runs where dropdown UDF = specific option) 5. Analyze individual test case execution results, status, and custom UDF metadata 6. Monitor test case run performance and execution trends 7. Generate detailed test execution reports including custom UDF data 8. Track test case run history and execution patterns 9. Validate test case run coverage and execution completeness 10. Audit test case run data with UDF values for compliance and quality assurance 11. Export detailed test case run data including Test Run UDFs for external reporting 12. Retrieve paginated test case run results for large test suite executions **Examples:** 1. Get all test case runs for test suite run ID '107021' ```json { "tsrunID": "107021", "viewId": 6887 } ``` Expected Output: Present as ONE unified table — never as a separate type+value breakdown. Example: | Test Case Key | Test Case Summary | Executed Version | Execution Status | Tested By | Environments UDF | Execution Type | Country | | MAC-TC-5 | Login - valid credential | v1 | Passed | varis | chrome, edge, safari | Functional | India > i3 | | MAC-TC-6 | Login - invalid password | v2 | Failed | john | firefox | Regression | - | Columns: Test Case Key (entityKey) | Test Case Summary (summary) | Executed Version (latestVersion) | Execution Status (runStatus) | then one column per UDF label. Use the UDF 'label' as column header. Show null UDF values as '-'. 2. Fetch Test Run UDF values for all executions in test suite run '728995' ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20 } ``` Expected Output: Present as ONE unified table combining identification fields and UDF values — never a separate type+value breakdown. Example: | Test Case Key | Test Case Summary | Executed Version | Execution Status | Tested By | Environments UDF | Planned Execution Date | Execution Type | | MAC-TC-5 | Login test | v1 | Passed | varis | chrome, edge, safari | - | Functional | HTML is stripped from LARGETEXT UDF fields. Null values shown as '-'. 3. Filter by Test Run UDF list/dropdown field (single-select or multi-select lookup) — runs where UDF '8260LUP' has list item IDs 5108701 or 5108697 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"}]" } ``` Expected Output: Filtered test case runs matching the lookup list UDF values 4. Filter by Test Run UDF multi-lookup list field — runs where multi-select UDF 'PGTE_MULTILOOKUPLIST' contains list item IDs 5126503 or 5126502 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5126503,5126502],\"field\":\"PGTE_MULTILOOKUPLIST\"}]" } ``` Expected Output: Filtered test case runs where multi-lookup UDF matches any of the given list item IDs 5. Filter by Test Run UDF cascading dropdown field — runs where cascading UDF 'cascade_vK' has list item IDs 5126498 or 5126499 (must set isCascading:true) ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5126498,5126499],\"field\":\"cascade_vK\",\"isCascading\":true}]" } ``` Expected Output: Filtered test case runs matching the cascading dropdown UDF values 6. Filter by Test Run UDF short text field — runs where text UDF 'TRString' contains the value 'str' ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"}]" } ``` Expected Output: Filtered test case runs where short text UDF matches the search string 7. Filter by Test Run UDF large text field — runs where large text UDF 'vk_large_text' contains 'this is large text' ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"string\",\"field\":\"vk_large_text\",\"value\":\"this is large text\"}]" } ``` Expected Output: Filtered test case runs where large text UDF matches the search string 8. Filter by Test Run UDF date field — runs where date UDF 'PGTE_DATEPICKER' is after a specific date (comparison: gt) and before another date (comparison: lt) ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"gt\",\"value\":\"06-01-2026\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"lt\",\"value\":\"06-30-2026\"}]" } ``` Expected Output: Filtered test case runs where date UDF falls within the specified range 9. Filter by Test Run UDF numeric field — runs where numeric UDF 'NB_number_TR' equals 2 ```json { "tsrunID": "728995", "viewId": 79451, "tcrUdfFilter": "[{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]" } ``` Expected Output: Filtered test case runs where numeric UDF equals the specified value 10. Combine multiple Test Run UDF filters — filter by list UDF AND string UDF AND numeric UDF simultaneously ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"},{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"},{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]" } ``` Expected Output: Test case runs matching ALL specified UDF filter conditions (AND logic) 11. Full filter combination — standard field filter + Test Run UDF filter + show only runs with defects ```json { "tsrunID": "728995", "viewId": 79451, "start": 0, "page": 1, "limit": 20, "filter": "[]", "udfFilter": "[]", "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701,5108697],\"field\":\"8260LUP\"},{\"type\":\"string\",\"field\":\"TRString\",\"value\":\"str\"},{\"type\":\"string\",\"field\":\"vk_large_text\",\"value\":\"this is large text\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"gt\",\"value\":\"\"},{\"type\":\"date\",\"field\":\"PGTE_DATEPICKER\",\"comparison\":\"lt\",\"value\":\"\"},{\"type\":\"list\",\"value\":[5126503,5126502],\"field\":\"PGTE_MULTILOOKUPLIST\"},{\"type\":\"list\",\"value\":[5126498,5126499],\"field\":\"cascade_vK\",\"isCascading\":true},{\"type\":\"numeric\",\"value\":2,\"field\":\"NB_number_TR\"}]", "showTcWithDefects": false } ``` Expected Output: Test case runs filtered by all 7 UDF field type conditions simultaneously 12. Get paginated test case runs with standard runStatus filter ```json { "tsrunID": "2362144", "viewId": 104123, "start": 0, "page": 1, "limit": 25, "filter": "[{\"type\":\"string\",\"value\":\"Failed\",\"field\":\"runStatus\"}]" } ``` Expected Output: Paginated list of Failed test case runs with 25 items per page including testRunUdfs 13. Show only test case runs with linked defects, filtered by Test Run UDF list value ```json { "tsrunID": "107021", "viewId": 6887, "showTcWithDefects": true, "tcrUdfFilter": "[{\"type\":\"list\",\"value\":[5108701],\"field\":\"8260LUP\"}]" } ``` Expected Output: Test case runs with defects where the specified Test Run UDF matches **Hints:** 1. === MANDATORY RESPONSE FORMAT — READ THIS BEFORE RENDERING ANY OUTPUT === 2. 3. PIVOT RULE — CRITICAL: 4. The 'testRunUdfs' field on each row is a key-value map (object) of UDF field keys to their values. 5. You MUST pivot this into TABLE COLUMNS — do NOT render it as rows. 6. → Each key in testRunUdfs = use the UDF human-readable label as the column header 7. → Each value in testRunUdfs = the cell value for that run's row 8. → 'fieldType' / 'fieldID' = INTERNAL METADATA — NEVER show these as columns 9. 10. FORBIDDEN PATTERNS — NEVER do any of these: 11. ❌ Do NOT render a separate sub-table (Label | Type | Value) per tcRunID 12. ❌ Do NOT show 'Type' or 'fieldType' as a visible column 13. ❌ Do NOT group output by tcRunID with individual breakdowns beneath each 14. ❌ Do NOT show raw UDF field keys (e.g. 'TRString', '8260LUP') as column headers — use human-readable labels 15. 16. REQUIRED OUTPUT — ONE unified table, all runs as rows: 17. | Test Case Key | Test Case Summary | Executed Version | Execution Status | Linked Defects (Execution) | Linked Defects (Steps) | <UDF Label 1> | <UDF Label 2> | ... | 18. |---------------|-------------------|------------------|------------------|-----------------------------|-------------------------|---------------|---------------|-----| 19. | VKMCP-TC-1 | Login test | v1 | Not Run | 1 | 0 | varis | chrome, edge | ... | 20. | VKMCP-TC-2 | Invalid password | v2 | Not Run | 0 | 2 | john | firefox | ... | 21. 22. MANDATORY COLUMNS (always first, in this order): 23. 1. Test Case Key → entityKey (e.g. 'VKMCP-TC-1') 24. 2. Test Case Summary → summary (test case name) 25. 3. Executed Version → latestVersion (e.g. 'v1', 'v2') 26. 4. Execution Status → runStatus (e.g. 'Not Run', 'Passed', 'Failed') 27. 5. Linked Defects (Execution) → linkedDfCount (defects/issues linked to the test case run itself) 28. 6. Linked Defects (Steps) → linkedStepDfCount (defects/issues linked to that run's test step executions) 29. 7. Tested By → testedBy/executedBy when present 30. 8+. One column per UDF field — use the human-readable label as header, the value as the cell. 31. NEVER combine columns 5 and 6 into a single 'Issues Linked' count — they are always reported separately, defaulting to 0 when absent. 32. 33. Null UDF values → show as '-' in the cell. 34. If testRunUdfs is empty or hasTcRunUdf is false, still show columns 1-5. 35. CHAINING WITH FETCH TEST RUN UDF VALUES: 36. If the user explicitly asks for Test Run UDFs with these test case runs, call 'Fetch Test Run UDF Values' after this tool with sourceContext='testSuiteRun' and sourceRows=<this response data>. Render that tool's unifiedTableRows as the final answer. 37. === END MANDATORY RESPONSE FORMAT === 38. 39. CRITICAL WORKFLOW FOR FETCHING ALL EXECUTIONS OF A TEST SUITE: 40. When user asks to: 41. - 'fetch all executions' 42. - 'get all test runs' 43. - 'fetch all tcRunIDs for test suite X' 44. - 'update status for all executions of test suite X' 45. STEP 1: First call FETCH_EXECUTIONS_BY_TESTSUITE tool with the test suite ID (tsID, not entityKey) 46. - This returns ALL execution records for that test suite (could be 3, 5, 9, or any number) 47. - Extract ALL tsRunID values from the response data array 48. - Example response: data: [{tsRunID: '2739237', ...}, {tsRunID: '2739236', ...}, {tsRunID: '2739235', ...}] 49. STEP 2: For EACH tsRunID from Step 1, call this tool (FETCH_TEST_CASE_RUNS_BY_TESTSUITE_RUN) 50. - This returns all test case runs (tcRunID values) for that specific execution 51. - Repeat for ALL tsRunID values discovered in Step 1 52. STEP 3: Collect all tcRunID values from all executions 53. - Now you have the complete list of test case runs across ALL executions 54. - Use these for bulk status updates or other operations 55. CRITICAL ERROR TO AVOID: 56. - NEVER assume or hard-code only 2-3 execution IDs 57. - NEVER skip Step 1 - always discover ALL executions first 58. - NEVER fetch tcRunIDs for only some executions - get ALL of them 59. - If there are 9 executions, you must fetch tcRunIDs for all 9, not just 2 60. EXAMPLE WORKFLOW: 61. User: 'Fetch all test case runs for test suite VKMCP-TS-21' 62. Step 1: Call FETCH_EXECUTIONS_BY_TESTSUITE with tsID (resolved from VKMCP-TS-21) 63. Result: Found 9 executions with tsRunIDs: 2739237, 2739236, 2739235, 2739234, 2739233, 2739232, 2739231, 2739230, 2739229 64. Step 2: Call this tool 9 times (once for each tsRunID) 65. Call 1: tsrunID='2739237' -> returns 54 tcRunIDs 66. Call 2: tsrunID='2739236' -> returns 54 tcRunIDs 67. ... (repeat for all 9) 68. Step 3: Total collected: 9 executions × 54 test cases = 486 total tcRunIDs 69. 70. PERFORMANCE CONSIDERATIONS FOR LARGE TEST RUNS: 71. When dealing with large numbers of test case runs (500+, 1000+), follow these guidelines: 72. 1. ALWAYS inform the user about the scale BEFORE starting operations: 73. Example: 'Found 9 executions with approximately 486 test case runs. This will require fetching data from all 9 executions and may take a moment.' 74. 2. For bulk status updates on 1000+ test case runs: 75. - NEVER attempt to update all 1000+ in a single operation 76. - Break into smaller batches of 10-20 test case runs per update 77. - Inform user: 'Found 1000 test case runs. Will process in batches of 20 to ensure reliability and performance.' 78. - Show progress: 'Processing batch 1/50 (20 test runs)...', 'Batch 2/50...' 79. 3. Recommended batch sizes: 80. - For status updates: 10-20 test case runs per batch 81. - For fetching data: Can handle larger batches (50-100) 82. - Adjust based on API response times and timeout limits 83. 4. Always provide progress updates for long-running operations: 84. - Before: 'Processing 1000 test runs in 50 batches of 20...' 85. - During: 'Completed 200/1000 test runs (10 batches)...' 86. - After: 'Successfully updated all 1000 test case runs.' 87. 5. Error handling for batch operations: 88. - If a batch fails, report which batch and continue with remaining 89. - Provide summary at the end: 'Completed 48/50 batches. 2 batches failed (batch 23, 45).' 90. - Allow user to retry failed batches specifically 91. EXAMPLE LARGE-SCALE WORKFLOW: 92. User: 'Update status to Failed for all test runs in VKMCP-TS-21' 93. Step 1: Discover all executions (9 found) 94. Step 2: Fetch all tcRunIDs (486 total) 95. Step 3: Inform user: 'Found 486 test case runs across 9 executions. Will update in 25 batches of 20 runs each.' 96. Step 4: Process in batches with progress updates 97. Step 5: Report completion: 'Successfully updated all 486 test case runs to Failed status.' 98. 99. CRITICAL: tsrunID and viewId parameters are REQUIRED 100. tsrunID is a STRING identifier for the test suite run execution 101. viewId is a NUMERIC identifier for the test execution view 102. !MOST IMPORTANT HOW TO GET tsrunID: 103. 1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE) to get ALL available executions 104. 2. From the response, get value of following attribute -> data[<index>].tsRunID for EVERY execution 105. 3. Example: Test Suite might have multiple executions with IDs '107021', '107022', '107023', etc. 106. 4. NEVER assume there are only 2-3 executions - always fetch to discover the actual count 107. !MOST IMPORTANT HOW TO GET viewId: 108. CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool. 109. The viewId parameter must be fetched from the active project's info (latestViews.TE.viewId). 110. Each QMetry project may have a different test execution viewId, so using a stale or incorrect viewId will result in incomplete or invalid test case run data. 111. Usage workflow: 112. 1. Fetch project info for the current project (Admin/Get info Service). 113. 2. Extract latestViews.TE.viewId from the response. 114. 3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call. 115. Example: 116. { 117. tsrunID: "2362144", 118. viewId: 104123, 119. start: 0, 120. page: 1, 121. limit: 25 122. } 123. This ensures the tool fetches the proper execution runs data for the selected project context. 124. SUPPORTED PARAMETERS: start, page, limit, tsrunID, viewId, filter, udfFilter, tcrUdfFilter, showTcWithDefects 125. PAGINATION: Use start, page, and limit for result pagination 126. PAYLOAD FORMAT: {"start": 0, "page": 1, "limit": 10, "tsrunID": "2362144", "viewId": 104123} 127. 128. === TEST RUN UDF (tcrUdfFilter) — ALL 7 FIELD TYPE FORMATS === 129. tcrUdfFilter filters test case RUNS by Test Run UDF values (not test case UDFs — use udfFilter for those). 130. Value is a JSON array string. Multiple conditions are combined with AND logic. 131. Base structure: {"type":"<fieldType>", "field":"<udfFieldKey>", "value":<value> [,"comparison":"..."] [,"isCascading":true]} 132. 133. --- TYPE 1: list (single-select lookup / dropdown) --- 134. Use for: single-select lookup list UDF fields (one value selected from a list). 135. value: array of numeric list item IDs — get IDs from FETCH_CUSTOM_LIST_ITEMS tool. 136. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>]} 137. Example: [{"type":"list","value":[5108701,5108697],"field":"8260LUP"}] 138. Matches runs where the UDF value is ANY of the provided list item IDs (OR within the array). 139. 140. --- TYPE 2: list (multi-select lookup list) --- 141. Use for: multi-select lookup list UDF fields (multiple values can be selected). 142. Syntax identical to single-select list — same format, just the UDF field itself is multi-select. 143. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>]} 144. Example: [{"type":"list","value":[5126503,5126502],"field":"PGTE_MULTILOOKUPLIST"}] 145. Matches runs where ANY of the UDF's selected values match any of the provided IDs. 146. 147. --- TYPE 3: list (cascading dropdown) --- 148. Use for: cascading dropdown UDF fields (parent-child linked dropdowns). MUST add isCascading:true. 149. Format: {"type":"list", "field":"<fieldKey>", "value":[<id1>,<id2>], "isCascading":true} 150. Example: [{"type":"list","value":[5126498,5126499],"field":"cascade_vK","isCascading":true}] 151. CRITICAL: missing isCascading:true on a cascading field will cause incorrect results or API error. 152. 153. --- TYPE 4: string (short text) --- 154. Use for: single-line text UDF fields. 155. value: the string to search for (partial match / contains). 156. Format: {"type":"string", "field":"<fieldKey>", "value":"<searchText>"} 157. Example: [{"type":"string","field":"TRString","value":"str"}] 158. 159. --- TYPE 5: string (large text / rich text) --- 160. Use for: multi-line or rich text UDF fields. Syntax is identical to short text string type. 161. Format: {"type":"string", "field":"<fieldKey>", "value":"<searchText>"} 162. Example: [{"type":"string","field":"vk_large_text","value":"this is large text"}] 163. NOTE: Search is against the raw (HTML) content stored in the field; plain text search terms work fine. 164. 165. --- TYPE 6: date --- 166. Use for: date picker UDF fields. REQUIRES a 'comparison' property. 167. comparison: 'gt' = after the date (greater than), 'lt' = before the date (less than). 168. value: date string in 'MM-DD-YYYY' format, or empty string '' to leave the bound open. 169. Format: {"type":"date", "field":"<fieldKey>", "comparison":"gt"|"lt", "value":"MM-DD-YYYY"} 170. Example — date range: [{"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"},{"type":"date","field":"PGTE_DATEPICKER","comparison":"lt","value":"06-30-2026"}] 171. Example — open-ended (no upper bound): [{"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"}] 172. To filter by a single date use two conditions (gt day-before AND lt day-after) or just one bound. 173. CRITICAL: 'comparison' field is mandatory for date type — omitting it causes API error. 174. 175. --- TYPE 7: numeric --- 176. Use for: number UDF fields. 177. value: a number (integer or decimal). 178. Format: {"type":"numeric", "field":"<fieldKey>", "value":<number>} 179. Example: [{"type":"numeric","value":2,"field":"NB_number_TR"}] 180. 181. --- COMBINING MULTIPLE FILTERS --- 182. All conditions in tcrUdfFilter array use AND logic — runs must satisfy ALL conditions. 183. Full example (all 7 types combined): 184. [ 185. {"type":"list","value":[5108701,5108697],"field":"8260LUP"}, 186. {"type":"list","value":[5126503,5126502],"field":"PGTE_MULTILOOKUPLIST"}, 187. {"type":"list","value":[5126498,5126499],"field":"cascade_vK","isCascading":true}, 188. {"type":"string","field":"TRString","value":"str"}, 189. {"type":"string","field":"vk_large_text","value":"large text"}, 190. {"type":"date","field":"PGTE_DATEPICKER","comparison":"gt","value":"06-01-2026"}, 191. {"type":"date","field":"PGTE_DATEPICKER","comparison":"lt","value":"06-30-2026"}, 192. {"type":"numeric","value":2,"field":"NB_number_TR"} 193. ] 194. --- FILTER PARAMETER SUMMARY --- 195. tcrUdfFilter: filter by Test Run UDF fields (this section) 196. udfFilter: filter by Test Case UDF fields (different from test run UDFs) 197. filter: filter by standard execution fields (runStatus, executedBy, etc.) 198. All three can be combined in a single request — they are independently applied with AND logic. 199. 200. hasTcRunUdf FLAG — IMPORTANT: 201. The response contains a 'hasTcRunUdf' boolean flag at the top level. 202. hasTcRunUdf: true → Project has Test Run UDFs configured; each record includes 'testRunUdfs' object. 203. hasTcRunUdf: false → Project has NO Test Run UDFs configured. 204. When hasTcRunUdf is false, the response includes a 'testRunUdfNote' with a professional explanation. 205. Inform the user: 'No Test Run UDFs are configured for this project. Contact a project administrator to set up Test Run UDF fields.' 206. NEVER attempt to read testRunUdfs from records when hasTcRunUdf is false — the field will not be present. 207. 208. TEST RUN UDF RESPONSE (testRunUdfs): 209. When the API returns Test Run UDF data, each row will include a 'testRunUdfs' object. 210. This is a key-value map of UDF field keys to their values, parsed from the API's 'udfjson' field. 211. HTML is stripped from rich text (large text) UDF fields for readable LLM output. 212. Example testRunUdfs in response: 213. testRunUdfs: { 214. "8260LUP": "l1", 215. "look_554": "99", 216. "cascade_vK": {"child": "aa", "parent": "abc"}, 217. "dateNJ": "06-02-2026", 218. "NB_Multilppup_TR": ["ahd"], 219. "Jal_Largetext": "asdef asdfads asdfasf asdf asdf asfd a sdfa" 220. } 221. Use pagination for large result sets (start, page, limit parameters) 222. This tool is essential for detailed test execution analysis and reporting 223. Critical for monitoring individual test case execution performance and UDF values 224. Use for compliance reporting and execution audit trails 225. Essential for test execution quality assurance and trend analysis
Input schema
Input schema unchanged.
11 unchanged entries
(schema root)filterlimitpageprojectKeyshowTcWithDefectsstarttcrUdfFiltertsrunIDudfFilterviewId
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_update_issueModifiedWhat changed
- qmetry_update_issue — Input type change: property affectedCycles changed: +items={"type":"number"}, type "number" → "array".
- qmetry_update_issue: description changed.
Why it could matter
- Arguments of the old type may no longer validate against the new schema.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate an existing QMetry issue by DefectId and/or entityKey. **Toolset:** Issues **Parameters:** - DefectId (number) *required*: ID of the defect/issue to be updated. CRITICAL: the parameter name is 'DefectId' (capital D) — do NOT use 'defectId', 'issueId', 'id', or other variants. Accepts a string or number. - entityKey (string): Entity Key of the defect/issue to be updated - issueType (number): Issue type ID (e.g. Bug, Enhancement, etc.) - issuePriority (number): Issue priority ID (e.g. High, Medium, Low, etc.) - summary (string): Summary or title of the defect/issue - description (string): Detailed description of the defect/issue - issueOwner (number): Owner/user ID for the issue - affectedRelease (number): Release IDs affected by this issue - affectedCycles (number): Cycle IDs affected by this issue - udfFields (record<string, union>): Flat UDF field values. Keys = UDF field names from 'Fetch UDF Layout'. Values depend on fieldTypeName: STRING/LARGETEXT: string, NUMBER: number, DATETIMEPICKER: date string ('14-08-2026'), LOOKUPLIST: numeric ID, MULTILOOKUPLIST: array of IDs [101, 102], CASCADINGLIST: { parent: 101, child: 102 }. Call 'Fetch UDF Layout' with entityType + pageName='ADD' to discover available fields and list option IDs. - UDF (record<string, object>): UDF wrapper required for update. Keys = UDF field names. Each value must include fieldID (from 'Fetch UDF Layout' with pageName='DETAIL') and value. **Output Description:** JSON object with update status and details. **Use Cases:** 1. Update issue summary (title) 2. Change issue priority, type, or owner 3. Update affected release or cycles 4. Update description or environment 5. Bulk update using DefectId and/or entityKey **Examples:** 1. Update issue summary ```json { "DefectId": 118150, "summary": "Money withdrawal is success even if insufficient amount_updated" } ``` Expected Output: Issue summary updated successfully. 2. Update issue priority ```json { "DefectId": 118150, "issuePriority": 189340 } ``` Expected Output: Issue priority updated successfully. 3. Update issue type ```json { "DefectId": 118150, "issueType": 189337 } ``` Expected Output: Issue type updated successfully. 4. Update affected release ```json { "DefectId": 118150, "affectedRelease": 3730 } ``` Expected Output: Affected release updated successfully. **Hints:** 1. === DEFAULT VALUES — APPLY FOR ANY UNSET FIELD === 2. ALWAYS call 'Fetch UDF Layout' with entityType='IS', pageName='DETAIL' before updating. 3. defaultValues (from Fetch UDF Layout, i.e. qmDefaultValue.IS): { fieldName: defaultValueId } — sweep ALL entries. 4. defaultValues can contain BOTH system field defaults AND UDF field defaults — handle each differently: 5. → SYSTEM field defaults (fields in qmSDF.IS, e.g. component/Labels, issueType, issuePriority): route to TOP-LEVEL params, NOT to udfFields. 6. - MULTILOOKUPLIST system fields (e.g. component): default is a single ID — wrap in array: component: [5232632]. 7. - LOOKUPLIST system fields (e.g. issueType, issuePriority): default is a single ID — use directly. 8. → UDF field defaults (fields in qmUDF.IS, e.g. str1, lookup19, age19): route to udfFields param. 9. For EACH key in defaultValues: if user did not explicitly provide that field → include it in payload using default, routed correctly. 10. This applies to non-mandatory fields too (e.g. component/Labels). Omitting them = data loss. 11. IMPORTANT: QMetry's API sometimes returns 'defaultValues: {}' (empty) — if so, skip auto-apply and ask user for mandatory fields without defaults. 12. systemFields (from qmSDF.IS): isMandatory=true fields must retain a valid value after update. 13. IMPORTANT: QMetry's API sometimes returns 'systemFields: []' (empty). If so, treat summary, issueType, issuePriority as always mandatory. 14. fields/UDF (from qmUDF.IS): isMandatory=true UDF fields must be included if being changed. 15. === END DEFAULT VALUES === 16. 17. === DATE FORMAT CHECK (MANDATORY — EVERY UPDATE REQUEST) === 18. ALWAYS call 'Fetch QMetry Project Info' before every update request — not only when the user explicitly mentions a date. 19. Any UDF field could be a DATETIMEPICKER. Wrong format causes QMetry to silently discard the field value (API returns success but value is NOT stored — no error). 20. STEP 1: From project info, read dateTimeFormatID (e.g. 3). 21. STEP 2: Find entry in dateTimeFormatNew where id === dateTimeFormatID → read its unique_value (e.g. 'yyyy-MM-dd'). 22. STEP 3: unique_value pattern: yyyy=4-digit year, MM=2-digit month (01-12), dd=2-digit day, MMM=3-letter month (Jan/Feb/...). 23. Example: id=1 → MM-dd-yyyy → '10-25-2000' | id=2 → dd-MM-yyyy → '25-10-2000' | id=3 → yyyy-MM-dd → '2000-10-25' | id=4 → dd-MMM-yyyy → '25-Oct-2000' 24. STEP 4: For EVERY DATETIMEPICKER field in the payload: parse any user-provided date and re-format it using the active unique_value pattern before sending. 25. NEVER assume a date format — always derive it from dateTimeFormatID. Wrong format = silent data loss. 26. === END DATE FORMAT CHECK === 27. 28. To get the DefectId, call the Issue/Fetch issue tool and use data[<index>].id from the response. 29. if you have pass issue key (VT-IS-5, MAC-IS-10 etc.) then first fetch issue by issue key to get issue id. 30. Along with DefectId, pass only those fields which are to be updated. 31. Refer to the Create Issue tool for valid field mappings and values. 32. You can update summary, priority, type, affectedRelease, affectedCycles, description, sync_with, issueOwner, component, environment, tcRunID, etc. 33. If you provide entityKey, it will be used for additional validation but DefectId is required. 34. 35. UDF (User Defined Fields) WORKFLOW FOR UPDATE: 36. 1. Call 'Fetch UDF Layout' with entityType='IS', pageName='DETAIL' to get field names, fieldIDs (projectUserFieldID), and list option IDs. 37. IF listOptions[field.listName] is empty after Fetch UDF Layout, the tool already tried a metadata fallback. If STILL empty, ask the user to provide the option ID from the QMetry UI — do NOT guess numeric IDs. 38. 2. For LOOKUPLIST fields: pick one ID from listOptions[field.listName][].id. 39. 3. For MULTILOOKUPLIST fields: pick array of IDs; also pass alias flat key (e.g., fieldNameAlias: 'Option Label'). 40. 4. For CASCADINGLIST fields: pick parent ID + fetch child with 'Fetch Cascade Child Values'. Pass { parent: parentId, child: childId }. 41. 5. Pass BOTH 'udfFields' (flat root values) AND 'UDF' wrapper (with fieldID) — both required for update. 42. Example: udfFields: { is_field: 'value' }, UDF: { is_field: { fieldID: 3001, value: 'value' } } 43. 6. Mandatory UDF fields (isMandatory=true) MUST be included.
- CurrentUpdate an existing QMetry issue by DefectId and/or entityKey. **Toolset:** Issues **Parameters:** - DefectId (number) *required*: ID of the defect/issue to be updated. CRITICAL: the parameter name is 'DefectId' (capital D) — do NOT use 'defectId', 'issueId', 'id', or other variants. Accepts a string or number. - entityKey (string): Entity Key of the defect/issue to be updated - issueType (number): Issue type ID (e.g. Bug, Enhancement, etc.) - issuePriority (number): Issue priority ID (e.g. High, Medium, Low, etc.) - summary (string): Summary or title of the defect/issue - description (string): Detailed description of the defect/issue - issueOwner (number): Owner/user ID for the issue - affectedRelease (number): Release IDs affected by this issue - affectedCycles (array): Cycle IDs affected by this issue - udfFields (record<string, union>): Flat UDF field values. Keys = UDF field names from 'Fetch UDF Layout'. Values depend on fieldTypeName: STRING/LARGETEXT: string, NUMBER: number, DATETIMEPICKER: date string ('14-08-2026'), LOOKUPLIST: numeric ID, MULTILOOKUPLIST: array of IDs [101, 102], CASCADINGLIST: { parent: 101, child: 102 }. Call 'Fetch UDF Layout' with entityType + pageName='ADD' to discover available fields and list option IDs. - UDF (record<string, object>): UDF wrapper required for update. Keys = UDF field names. Each value must include fieldID (from 'Fetch UDF Layout' with pageName='DETAIL') and value. **Output Description:** JSON object with update status and details. **Use Cases:** 1. Update issue summary (title) 2. Change issue priority, type, or owner 3. Update affected release or cycles 4. Update description or environment 5. Bulk update using DefectId and/or entityKey **Examples:** 1. Update issue summary ```json { "DefectId": 118150, "summary": "Money withdrawal is success even if insufficient amount_updated" } ``` Expected Output: Issue summary updated successfully. 2. Update issue priority ```json { "DefectId": 118150, "issuePriority": 189340 } ``` Expected Output: Issue priority updated successfully. 3. Update issue type ```json { "DefectId": 118150, "issueType": 189337 } ``` Expected Output: Issue type updated successfully. 4. Update affected release and affected cycles ```json { "DefectId": 118150, "affectedRelease": 3730, "affectedCycles": [ 1168 ] } ``` Expected Output: Affected release and affected cycles updated successfully. **Hints:** 1. === DEFAULT VALUES — APPLY FOR ANY UNSET FIELD === 2. ALWAYS call 'Fetch UDF Layout' with entityType='IS', pageName='DETAIL' before updating. 3. defaultValues (from Fetch UDF Layout, i.e. qmDefaultValue.IS): { fieldName: defaultValueId } — sweep ALL entries. 4. defaultValues can contain BOTH system field defaults AND UDF field defaults — handle each differently: 5. → SYSTEM field defaults (fields in qmSDF.IS, e.g. component/Labels, issueType, issuePriority): route to TOP-LEVEL params, NOT to udfFields. 6. - MULTILOOKUPLIST system fields (e.g. component): default is a single ID — wrap in array: component: [5232632]. 7. - LOOKUPLIST system fields (e.g. issueType, issuePriority): default is a single ID — use directly. 8. → UDF field defaults (fields in qmUDF.IS, e.g. str1, lookup19, age19): route to udfFields param. 9. For EACH key in defaultValues: if user did not explicitly provide that field → include it in payload using default, routed correctly. 10. This applies to non-mandatory fields too (e.g. component/Labels). Omitting them = data loss. 11. IMPORTANT: QMetry's API sometimes returns 'defaultValues: {}' (empty) — if so, skip auto-apply and ask user for mandatory fields without defaults. 12. systemFields (from qmSDF.IS): isMandatory=true fields must retain a valid value after update. 13. IMPORTANT: QMetry's API sometimes returns 'systemFields: []' (empty). If so, treat summary, issueType, issuePriority as always mandatory. 14. fields/UDF (from qmUDF.IS): isMandatory=true UDF fields must be included if being changed. 15. === END DEFAULT VALUES === 16. 17. === DATE FORMAT CHECK (MANDATORY — EVERY UPDATE REQUEST) === 18. ALWAYS call 'Fetch QMetry Project Info' before every update request — not only when the user explicitly mentions a date. 19. Any UDF field could be a DATETIMEPICKER. Wrong format causes QMetry to silently discard the field value (API returns success but value is NOT stored — no error). 20. STEP 1: From project info, read dateTimeFormatID (e.g. 3). 21. STEP 2: Find entry in dateTimeFormatNew where id === dateTimeFormatID → read its unique_value (e.g. 'yyyy-MM-dd'). 22. STEP 3: unique_value pattern: yyyy=4-digit year, MM=2-digit month (01-12), dd=2-digit day, MMM=3-letter month (Jan/Feb/...). 23. Example: id=1 → MM-dd-yyyy → '10-25-2000' | id=2 → dd-MM-yyyy → '25-10-2000' | id=3 → yyyy-MM-dd → '2000-10-25' | id=4 → dd-MMM-yyyy → '25-Oct-2000' 24. STEP 4: For EVERY DATETIMEPICKER field in the payload: parse any user-provided date and re-format it using the active unique_value pattern before sending. 25. NEVER assume a date format — always derive it from dateTimeFormatID. Wrong format = silent data loss. 26. === END DATE FORMAT CHECK === 27. 28. To get the DefectId, call the Issue/Fetch issue tool and use data[<index>].id from the response. 29. if you have pass issue key (VT-IS-5, MAC-IS-10 etc.) then first fetch issue by issue key to get issue id. 30. Along with DefectId, pass only those fields which are to be updated. 31. Refer to the Create Issue tool for valid field mappings and values. 32. You can update summary, priority, type, affectedRelease, affectedCycles, description, sync_with, issueOwner, component, environment, tcRunID, etc. 33. If you provide entityKey, it will be used for additional validation but DefectId is required. 34. 35. UDF (User Defined Fields) WORKFLOW FOR UPDATE: 36. 1. Call 'Fetch UDF Layout' with entityType='IS', pageName='DETAIL' to get field names, fieldIDs (projectUserFieldID), and list option IDs. 37. IF listOptions[field.listName] is empty after Fetch UDF Layout, the tool already tried a metadata fallback. If STILL empty, ask the user to provide the option ID from the QMetry UI — do NOT guess numeric IDs. 38. 2. For LOOKUPLIST fields: pick one ID from listOptions[field.listName][].id. 39. 3. For MULTILOOKUPLIST fields: pick array of IDs; also pass alias flat key (e.g., fieldNameAlias: 'Option Label'). 40. 4. For CASCADINGLIST fields: pick parent ID + fetch child with 'Fetch Cascade Child Values'. Pass { parent: parentId, child: childId }. 41. 5. Pass BOTH 'udfFields' (flat root values) AND 'UDF' wrapper (with fieldID) — both required for update. 42. Example: udfFields: { is_field: 'value' }, UDF: { is_field: { fieldID: 3001, value: 'value' } } 43. 6. Mandatory UDF fields (isMandatory=true) MUST be included.
Input schema
Property Previous (0.42.0) Current (0.43.0) Change affectedCyclesnumberoptional arrayoptional - Type changed
type: "number" → "array"affectedCycles › [items]not present number - Added
11 unchanged entries
(schema root)DefectIdUDFaffectedReleasedescriptionentityKeyissueOwnerissuePriorityissueTypesummaryudfFields
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
qmetry_update_test_caseModifiedWhat changed
- qmetry_update_test_case — Schema change: input property added: testcaseOwner.
- qmetry_update_test_case — Schema change: input property removed: owner.
- qmetry_update_test_case: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate an existing QMetry test case OR create a new version by tcID and tcVersionID, with auto-resolution from entityKey. **Toolset:** Test Cases **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tcID (number) *required*: Test Case numeric ID. CRITICAL: the parameter name is 'tcID' — do NOT use 'testCaseId', 'testCaseID', 'tcId', or other variants. Accepts a string or number. This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results or by using filters. - tcVersionID (number) *required*: Test Case version number. This is the internal numeric identifier for the version. - tcVersion (number): Test Case version number (required when withVersion=true for creating new version). This is the current version number from which a new version will be created. - withVersion (boolean): Pass 'true' if you want to create a new version of the test case with incremented version number. When true, a new version is created (e.g., if current version is 2, new version 3 is created). When false or omitted, updates the existing version specified by tcVersionID. IMPORTANT: Always send proper tcVersionID to identify which version the request is for. - versionComment (string): Comment or description for the new version (used only when withVersion=true). Helps track what changed in this new version. Example: 'Updated test steps for new requirements' - notruncurrent (boolean): Flag to control execution behavior for current version when creating a new version. Used in conjunction with withVersion=true. - notrunall (boolean): Flag to control execution behavior for all versions when creating a new version. Used in conjunction with withVersion=true. - folderPath (string): Folder path for test suites - SYSTEM AUTOMATICALLY SETS TO ROOT. Leave empty unless you want specific folder. System will automatically use empty string "" (root directory). Only specify if user wants specific folder like "Automation/Regression". (default: "") - scope (string): Scope of the operation - defines the context for data retrieval. Common values: 'project' (default), 'folder', 'release', 'cycle'. Applies to any entity type being fetched or operated upon. (default: "project") - isStepUpdated (boolean): Set to true when steps are being added, updated, or removed. Required when including 'steps' or 'removeSteps' arrays. - steps (array) - removeSteps (array) - name (string) - priority (number) - component (array) - owner (number) - testCaseState (number) - testCaseType (number) - estimatedTime (number): Estimated execution time in seconds. Example: 7200 for 2 hours - executionMinutes (number) - testingType (number) - description (string) - updateOnlyMetadata (boolean): Set to true to update only metadata fields without touching test steps. When true, steps and removeSteps are ignored. - udfFields (record<string, union>): Flat UDF field values. Keys = UDF field names from 'Fetch UDF Layout'. Values depend on fieldTypeName: STRING/LARGETEXT: string, NUMBER: number, DATETIMEPICKER: date string ('14-08-2026'), LOOKUPLIST: numeric ID, MULTILOOKUPLIST: array of IDs [101, 102], CASCADINGLIST: { parent: 101, child: 102 }. Call 'Fetch UDF Layout' with entityType + pageName='ADD' to discover available fields and list option IDs. - UDF (record<string, object>): UDF wrapper required for update operations. Keys = UDF field names. Each value must include fieldID (from 'Fetch UDF Layout' with pageName='DETAIL') and value. Also set matching flat key in udfFields for the LOOKUPLIST Alias display. Example: { custom_text: { fieldID: 1001, value: 'new value' } } **Output Description:** JSON object containing the test case ID, version ID, summary, update/creation metadata. When withVersion=true (version creation), response includes new version number and version ID. When withVersion=false/omitted (existing version update), response includes updated fields confirmation. **Use Cases:** 1. Update test case summary (name) 2. Change priority, owner, or state of a test case 3. Edit, add, or remove test steps 4. Update only metadata (no steps) 5. Create a new version of a test case (withVersion=true) 6. Update a specific version of a test case (without withVersion flag) 7. Bulk update using entityKey auto-resolution 8. Modify test case description or estimated time 9. Change test case type or component 10. Update testing type or custom fields 11. Update, add and remove test case steps 12. Version control for test case evolution tracking **Examples:** 1. Update test case summary (existing version update) ```json { "tcID": 4519260, "tcVersionID": 5448492, "name": "MAC Test11" } ``` Expected Output: Test case summary updated. tcID and tcVersionID auto-resolved from entityKey. Only 'name' field changed. Version remains the same. 2. Create NEW VERSION with updated summary and description ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Add two numbers 2 v2", "description": "Test Description version 2", "withVersion": true, "versionComment": "version 2 comment add", "notruncurrent": true, "notrunall": true } ``` Expected Output: New version created (version 2). Test case now has incremental version with updated summary and description. Original version 1 remains unchanged. 3. Create NEW VERSION with all metadata fields (release, cycle, priority, owner, etc.) ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Facebook Login Validation Failed update from MCP V2", "description": "Existing description V2", "priority": 2355751, "testcaseOwner": 6963, "testCaseState": 2355753, "testCaseType": 2355762, "estimatedTime": 7200, "withVersion": true, "versionComment": "Created version 2 with updated metadata", "notruncurrent": true, "notrunall": true, "folderPath": 602290, "scope": "project" } ``` Expected Output: New test case version 2 created with updated summary, description, priority (High), owner (umang.savaliya), state, type, and estimated time (2 hours). Version comment added for tracking. 4. Update EXISTING VERSION 2 (not creating new version) ```json { "tcID": 4572654, "tcVersionID": 5514385, "name": "Updated version 2 name", "priority": 2355752 } ``` Expected Output: Version 2 updated with new name and priority. No new version created because withVersion flag is not set. This is a normal update of existing version. 5. Update priority to High and owner to john.doe (existing version) ```json { "tcID": 4519260, "tcVersionID": 5448492, "priority": 505015, "testcaseOwner": 6963 } ``` Expected Output: Priority and owner updated. Field IDs auto-resolved from project info. tcID/tcVersionID resolved from entityKey. Existing version modified. 6. Update steps (edit, add, remove) - existing version ```json { "tcID": 4519260, "tcVersionID": 5448492, "steps": [ { "orderId": 1, "description": "Step 22", "inputData": "Input 22", "expectedOutcome": "Outcome 22", "tcStepID": 3014032 }, { "orderId": 2, "description": "Step3", "inputData": "Input 3", "expectedOutcome": "Outcome 3" } ], "removeSteps": [ { "tcStepID": 3014031, "description": "Step 1", "orderId": 1 } ], "isStepUpdated": true } ``` Expected Output: Steps updated: Step 22 edited (tcStepID preserved), Step3 added (no tcStepID), Step 1 removed. tcID/tcVersionID auto-resolved. Existing version modified. 7. Create NEW VERSION with updated steps ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Add two numbers 2 v2", "steps": [ { "orderId": 1, "description": "I and u have a calculator", "inputData": "", "expectedOutcome": "", "tcStepID": 38001791 }, { "orderId": 2, "description": "I add 41 and 31", "inputData": "", "expectedOutcome": "", "tcStepID": 38001793 }, { "orderId": 3, "description": "the result should be 72", "inputData": "", "expectedOutcome": "", "tcStepID": 38001792 } ], "withVersion": true, "versionComment": "version 2 with preserved steps", "notruncurrent": true, "notrunall": true, "isStepUpdated": true } ``` Expected Output: New version 2 created with all steps from version 1 preserved. Steps carry forward with their tcStepID values. Version comment added for tracking. 8. Update only metadata (no steps) - existing version ```json { "tcID": 4519260, "tcVersionID": 5448492, "updateOnlyMetadata": true, "name": "New Name" } ``` Expected Output: Metadata updated only. Steps unchanged. tcID/tcVersionID auto-resolved. Existing version modified. 9. Create NEW VERSION from existing version 2 with updated steps (working payload for linked test cases) ```json { "tcID": 4594145, "tcVersionID": 5536706, "tcVersion": 2, "name": "Mock Test Case - E-commerce Checkout Flow - v3", "steps": [ { "orderId": 1, "description": "Open browser and navigate to e-commerce website", "expectedOutcome": "Homepage loads successfully with product catalog", "inputData": "URL: https://example-shop.com", "tcStepID": 38129471 }, { "orderId": 2, "description": "Search for product", "expectedOutcome": "Search results display relevant products", "inputData": "Search term: 'wireless headphones'", "tcStepID": 38129475 }, { "orderId": 3, "description": "Select product and add to cart", "expectedOutcome": "Product added to cart, cart counter increments", "inputData": "Click 'Add to Cart' button", "tcStepID": 38129472 }, { "orderId": 4, "description": "Proceed to checkout", "expectedOutcome": "Checkout page displays with cart summary", "inputData": "Click cart icon and 'Proceed to Checkout'", "tcStepID": 38129473 }, { "orderId": 5, "description": "Complete payment", "expectedOutcome": "Order confirmation page displayed", "inputData": "Fill payment details and submit", "tcStepID": 38129474 }, { "orderId": 6, "description": "Verify order confirmation email received", "expectedOutcome": "Email with order details received in inbox", "inputData": "Check email account for confirmation" }, { "orderId": 7, "description": "Check order status in account dashboard", "expectedOutcome": "Order status shows as 'Processing' with tracking information", "inputData": "Navigate to My Orders section" } ], "withVersion": true, "versionComment": "Created version 3: Added 2 new verification steps (email and order status check)", "notrunall": false, "notruncurrent": false, "scope": "project" } ``` Expected Output: New version 3 created successfully from version 2. Test case now has 7 steps (5 preserved + 2 new). Key: tcVersion=2 was used because version 2 already existed in system. notrunall and notruncurrent both false (not true). Result shows tcVersion: 3 in response with new tcVersionID. **Hints:** 1. === DEFAULT VALUES — APPLY FOR ANY UNSET FIELD === 2. Call 'Fetch UDF Layout' with entityType='TC', pageName='DETAIL' before updating. 3. defaultValues (from Fetch UDF Layout): { fieldName: defaultValueId } — sweep ALL entries. 4. For EACH key in defaultValues: if user did not explicitly provide that field → include it in payload with the default value. 5. This applies to non-mandatory fields too (e.g. priority, estimatedTime). Omitting them = data loss. 6. === END DEFAULT VALUES === 7. 8. === DATE FORMAT CHECK (MANDATORY — EVERY UPDATE REQUEST) === 9. ALWAYS call 'Fetch QMetry Project Info' before every update request — not only when the user explicitly mentions a date. 10. Any UDF field could be a DATETIMEPICKER. Wrong format causes QMetry to silently discard the field value (API returns success but value is NOT stored — no error). 11. STEP 1: From project info, read dateTimeFormatID (e.g. 3). 12. STEP 2: Find entry in dateTimeFormatNew where id === dateTimeFormatID → read its unique_value (e.g. 'yyyy-MM-dd'). 13. STEP 3: unique_value pattern: yyyy=4-digit year, MM=2-digit month (01-12), dd=2-digit day, MMM=3-letter month (Jan/Feb/...). 14. Example: id=1 → MM-dd-yyyy → '10-25-2000' | id=2 → dd-MM-yyyy → '25-10-2000' | id=3 → yyyy-MM-dd → '2000-10-25' | id=4 → dd-MMM-yyyy → '25-Oct-2000' 15. STEP 4: For EVERY DATETIMEPICKER field in the payload: parse any user-provided date and re-format it using the active unique_value pattern before sending. 16. NEVER assume a date format — always derive it from dateTimeFormatID. Wrong format = silent data loss. 17. === END DATE FORMAT CHECK === 18. 19. CRITICAL - VERSION CREATION vs UPDATE DISTINCTION: 20. This tool supports TWO MODES using the SAME API endpoint: 21. 22. MODE 1: CREATE NEW VERSION (withVersion=true) 23. - Purpose: Create an incremental version of the test case (e.g., v1 → v2, v2 → v3) 24. - When to use: User explicitly asks to 'create new version', 'create version 2', 'increment version' 25. - Required fields: tcID, tcVersionID (of source version), tcVersion (current version number), withVersion=true 26. - Optional but recommended: versionComment (track what changed), notruncurrent, notrunall 27. - Behavior: Creates a NEW test case version with incremented version number. Source version remains unchanged. 28. - Example: If current version is 1, setting withVersion=true creates version 2 29. - Use cases: Updating test case for new requirements, creating variants for different scenarios, version control 30. 31. MODE 2: UPDATE EXISTING VERSION (withVersion=false or omitted) 32. - Purpose: Modify fields of an EXISTING version without creating a new version 33. - When to use: User asks to 'update test case', 'modify version X', 'change summary' (without mentioning new version) 34. - Required fields: tcID, tcVersionID (of version to update) 35. - Do NOT include: withVersion flag, versionComment, tcVersion 36. - Behavior: Updates the specified version in-place. No new version is created. 37. - Example: Updating version 2's summary - only version 2 is modified, no version 3 is created 38. - Use cases: Fixing typos, updating metadata, modifying steps in existing version 39. 40. CRITICAL FIELD UNDERSTANDING: 41. - tcVersionID: The VERSION ID (numeric identifier) of the version you're working with 42. - tcVersion: The VERSION NUMBER (1, 2, 3, etc.) - only needed when withVersion=true 43. - tcID: The TEST CASE ID (remains same across all versions) 44. - Example: Test case VKMCP-TC-10 (tcID: 4572654) has version 1 (tcVersionID: 5514384, tcVersion: 1) 45. - When creating version 2 from version 1: Send tcVersionID=5514384 (source), tcVersion=1 (current), withVersion=true 46. 47. HOW TO DETERMINE WHICH MODE: 48. - User says 'create new version' → MODE 1 (withVersion=true) 49. - User says 'create version 2' → MODE 1 (withVersion=true) 50. - User says 'update test case with new version' → MODE 1 (withVersion=true) 51. - User says 'update test case VKMCP-TC-10 summary' → MODE 2 (no withVersion, update existing version) 52. - User says 'update version 2 summary' → MODE 2 (no withVersion, update existing version 2) 53. - User says 'change priority of version 1' → MODE 2 (no withVersion, update version 1) 54. - If ambiguous, ask user: 'Do you want to create a new version or update the existing version?' 55. 56. VERSION CREATION WORKFLOW (withVersion=true): 57. Step 1: Fetch test case details to get current tcID, tcVersionID, and tcVersion 58. Step 2: Optionally fetch current steps if they need to be preserved/modified 59. Step 3: Prepare payload with: 60. - tcID (test case ID) 61. - tcVersionID (source version ID to create from) 62. - tcVersion (current version number) 63. - withVersion: true (CRITICAL flag) 64. - versionComment (recommended: describe what changed) 65. - Updated fields (name, description, priority, steps, etc.) 66. - notruncurrent: true (recommended) 67. - notrunall: true (recommended) 68. Step 4: Call update API - a new version will be created with incremented version number 69. Step 5: New version inherits all fields from source version, with your specified updates applied 70. 71. EXISTING VERSION UPDATE WORKFLOW (no withVersion): 72. Step 1: Fetch test case details to get tcID and tcVersionID of the version to update 73. Step 2: Prepare payload with: 74. - tcID (test case ID) 75. - tcVersionID (version ID to update) 76. - DO NOT include withVersion, versionComment, or tcVersion 77. - Only include fields you want to change 78. Step 3: Call update API - specified version is updated in-place 79. Step 4: No new version is created, only specified fields are modified 80. 81. FIELD MAPPING FOR VERSION CREATION: 82. When creating a new version, include ALL fields you want the new version to have: 83. - name: Test case summary (required if different from source) 84. - description: Test case description (required if different from source) 85. - priority: Priority ID (get from project info customListObjs.priority[index].id) 86. - testcaseOwner: Owner ID (get from project info customListObjs.owner[index].id) 87. - testCaseState: State ID (get from project info customListObjs.testCaseState[index].id) 88. - testCaseType: Type ID (get from project info customListObjs.testCaseType[index].id) 89. - testingType: Testing type ID (get from project info customListObjs.testingType[index].id) 90. - component: Array of component IDs (get from project info customListObjs.component[index].id) 91. - estimatedTime: Time in seconds (e.g., 7200 for 2 hours) 92. - steps: Array of step objects (include tcStepID from source version to preserve steps) 93. - folderPath: Folder path or folder ID 94. - scope: Usually 'project' 95. 96. STEPS HANDLING IN VERSION CREATION: 97. When creating a new version WITH steps: 98. - To PRESERVE existing steps: Include them with their original tcStepID values 99. - To ADD new steps: Include them WITHOUT tcStepID 100. - To MODIFY steps: Include them with tcStepID and updated description/data 101. - To REMOVE steps: Include them in removeSteps array 102. - Set isStepUpdated: true if any steps are modified, added, or removed 103. - If no steps are included, new version may inherit steps from source (verify with QMetry docs) 104. 105. If user provides entityKey (e.g., MAC-TC-1684), first call FETCH_TEST_CASES with a filter on entityKeyId to resolve the tcID and tcVersionID. 106. To get valid values for priority, owner, component, etc., call the project info tool and use the returned customListObjs IDs. 107. If the user provides a priority name (e.g. 'Blocker'), fetch project info, find the matching priority in customListObjs.priority[index].name, and use its ID in the payload. If the name is not found, skip the priority field (it is not required) and show a user-friendly message: 'Test case updated without priority, as given priority is not available in the current project.' 108. If the user provides a component name, fetch project info, find the matching component in customListObjs.component[index].name, and use its ID in the payload. If the name is not found, skip the component field (it is not required) and show a user-friendly message: 'Test case updated without component, as given component is not available in the current project.' 109. If the user provides an owner name, fetch project info, find the matching owner in customListObjs.owner[index].name, and use its ID in the payload as testcaseOwner. If the name is not found, skip the testcaseOwner field (it is not required) and show a user-friendly message: 'Test case updated without owner, as given owner is not available in the current project.' 110. If the user provides a test case state name, fetch project info, find the matching state in customListObjs.testCaseState[index].name, and use its ID in the payload as testCaseState. If the name is not found, skip the testCaseState field (it is not required) and show a user-friendly message: 'Test case updated without test case state, as given state is not available in the current project.' 111. If the user provides a test case type name, fetch project info, find the matching type in customListObjs.testCaseType[index].name, and use its ID in the payload as testCaseType. If the name is not found, skip the testCaseType field (it is not required) and show a user-friendly message: 'Test case updated without test case type, as given type is not available in the current project.' 112. If the user provides a testing type name, fetch project info, find the matching type in customListObjs.testingType[index].name, and use its ID in the payload as testingType. If the name is not found, skip the testingType field (it is not required) and show a user-friendly message: 'Test case updated without testing type, as given testing type is not available in the current project.' 113. Example: If user says 'Update test case with title "High priority test case" and set priority to "Blocker"', first call project info, map 'Blocker' to its ID, and use that ID for the priority field in the update payload. If user says 'set priority to "Urgent"' and 'Urgent' is not found, skip the priority field and show: 'Test case updated without priority, as given priority is not available in the current project.' 114. CRITICAL: To update test case steps without **Duplication**, use the following rules: 115. - ANTI-DUPLICATION RULE: The tcStepID field is THE KEY to prevent duplication: 116. * WITH tcStepID = UPDATE existing step (QMetry modifies the existing step in place) 117. * WITHOUT tcStepID = CREATE new step (QMetry adds a brand new step) 118. - For steps to be UPDATED: ALWAYS fetch existing steps first using FETCH_TEST_CASE_STEPS, then include the tcStepID in the step object. 119. - For steps to be ADDED: omit tcStepID completely in the step object. 120. - For steps to be REMOVED: add a full removeSteps object for each step to be deleted, matching the removeTestCaseStep interface. 121. - CRITICAL WARNING - DO NOT ADD UNSOLICITED STEPS: 122. * ONLY add, edit, or remove steps that the user EXPLICITLY requested 123. * DO NOT invent, create, or add extra steps based on assumptions or best practices 124. * DO NOT add 'helpful' steps that the user did not ask for 125. * When user says 'remove step 1', the result should have (N-1) steps, not N steps with extras 126. * When user says 'add 1 step', ONLY add that 1 step, nothing more 127. * When user says 'update step 2', ONLY update step 2, do not add or modify other steps 128. * If unsure what user wants, ASK first rather than adding steps autonomously 129. - WORKFLOW TO AVOID DUPLICATION: 130. 1. Call FETCH_TEST_CASE_STEPS to get all existing steps with their tcStepID values 131. 2. For steps you want to KEEP/UPDATE: Include them in steps[] WITH their original tcStepID 132. 3. For steps you want to ADD: Include them in steps[] WITHOUT tcStepID (ONLY if user requested) 133. 4. For steps you want to REMOVE: Include them in removeSteps[] with full details 134. 5. Always set isStepUpdated: true if steps are added, updated, or removed 135. 6. VERIFY your steps array matches user's explicit request (count and content) 136. - Example: If user says 'Edit step 1 to say ...', FIRST fetch steps to get tcStepID for step 1, THEN include it in the steps array with updated fields and the ORIGINAL tcStepID. 137. - Example: If user says 'Add a new step after step 2', add EXACTLY ONE new object to steps array with no tcStepID (not multiple steps). 138. - Example: If user says 'Remove step 3', add the full step object to removeSteps array, including tcStepID and all required fields. Do NOT add replacement steps. 139. - Example: If test case has 3 steps and user says 'remove step 1', result should have 2 steps (step 2 and step 3 with updated orderIds), NOT 3 steps with extras. 140. - Example: If user says 'add one mock step', add EXACTLY ONE step (not 2 or 3 steps even if they seem related). 141. - COMPLETE PAYLOAD EXAMPLE: { tcID: 123, tcVersionID: 456, steps: [{tcStepID: 1001, orderId: 1, description: 'Updated'}, {orderId: 2, description: 'New'}], removeSteps: [{tcStepID: 1002, orderId: 3, ...}], isStepUpdated: true } 142. - If only metadata is updated (no steps), set updateOnlyMetadata: true and do not include steps/removeSteps. 143. - Always preserve orderId sequence for proper step ordering. 144. - If user prompt is ambiguous, ask for clarification or show a user-friendly error. 145. - WARNING: Omitting tcStepID for existing steps will cause DUPLICATION - the API will create duplicates instead of updating! 146. - FINAL VERIFICATION BEFORE SENDING REQUEST: 147. * Count steps in your payload vs what user requested 148. * If user said 'add 1 step', steps array should have (existing_count + 1) items total 149. * If user said 'remove 1 step', steps array should have (existing_count - 1) items total, removeSteps should have 1 item 150. * If user said 'update step X', steps array should have same count as before, with step X's tcStepID preserved 151. * NEVER include steps the user did not explicitly mention or request 152. Steps are optional but recommended for manual test cases. 153. If the user provides a prompt like 'update test case with steps as step 1 - Go to login page, step 2 - give credential, step 3 - go to test case page, step 4 - create test case', LLM should parse each step and convert it into the steps payload array, mapping each step to an object with orderId, description, and optionally inputData and expectedOutcome. 154. Example mapping: 'step 1 - Go to login page' → { orderId: 1, description: 'Go to login page' }. 155. LLM should increment orderId for each step, use the step text as description, and optionally infer inputData/expectedOutcome if provided in the prompt. 156. Demo steps payload: steps: [ { orderId: 1, description: 'First Step', inputData: 'First Data', expectedOutcome: 'First Outcome', UDF: { customField1: 'Custom Field Data A', customField2: 'Custom Field Data B' } }, ... ] 157. UDF fields in steps must match your QMetry custom field configuration. 158. All IDs (priority, owner, etc.) must be valid for your QMetry instance. 159. If a custom field is mandatory, include it in the UDF object. 160. 161. ADDITIONAL VERSION CREATION GUIDANCE: 162. - versionComment field: STRONGLY RECOMMENDED when withVersion=true. Helps track why version was created. 163. Example comments: 'Updated for Sprint 5 requirements', 'Fixed test steps based on code review', 'Version 2 for production environment' 164. - notruncurrent and notrunall flags: Control execution behavior when creating versions. Set both to true as best practice. 165. - folderPath: Can be string path or numeric folder ID. Usually inherited from source version if not specified. 166. - attachments: Use ADD/REMOVE arrays to manage attachments when creating new version or updating existing version. 167. - estimatedTime vs executionMinutes: Use estimatedTime (in seconds) for version creation. executionMinutes (in minutes) is legacy field. 168. 169. REAL-WORLD VERSION CREATION EXAMPLES: 170. Example 1: User says 'create a new version of test case VKMCP-TC-10 with summary = "Facebook Login Validation Failed update from MCP V2", description = used existing description by at last add V2 text, release = default, cycle = default' 171. → Workflow: 172. 1. Fetch VKMCP-TC-10 details to get tcID, tcVersionID, tcVersion, current description 173. 2. Fetch project info to get default release ID and cycle ID 174. 3. Append ' V2' to current description 175. 4. Send payload with: tcID, tcVersionID (source), tcVersion (current), withVersion=true, name='...V2', description='...V2', versionComment='Created version 2', release/cycle IDs 176. → Result: New incremental version created (e.g., version 1 → version 2) with updated summary, modified description, associated with default release/cycle 177. 178. Example 2: User says 'update version 2 summary, release, cycle, priority' 179. → Workflow: 180. 1. Fetch test case details to get version 2's tcVersionID 181. 2. Fetch project info to get priority, release, cycle IDs 182. 3. Send payload with: tcID, tcVersionID (of version 2), WITHOUT withVersion flag, with updated summary, release, cycle, priority 183. → Result: Version 2 updated in-place. No new version created. Only specified fields modified. 184. 185. COMMON PITFALLS TO AVOID: 186. - Pitfall 1: Setting withVersion=true when user wants to update existing version → Creates unwanted new version 187. - Pitfall 2: Omitting versionComment when creating new version → Lost tracking of why version was created 188. - Pitfall 3: Not fetching current tcVersionID before update → Updating wrong version or causing error 189. - Pitfall 4: Using tcVersion for normal updates → tcVersion only needed when withVersion=true 190. - Pitfall 5: Not including tcStepID for steps when creating version → Steps may duplicate instead of preserving 191. - Pitfall 6: Confusing tcVersionID (version identifier) with tcVersion (version number) → Wrong API payload 192. 193. CRITICAL ERROR HANDLING: TC.VERSION_NOT_SYNCED FOR LINKED TEST CASES 194. 195. PROBLEM: Test cases linked to test suites or with existing executions cannot be updated directly 196. TRIGGERS: 197. ✓ Test case is linked to one or more test suites 198. ✓ Test case has execution history (test runs exist) 199. ✓ Test case is part of a release/cycle with test runs 200. ✓ Any step modification when test case has associations 201. 202. ERROR CODE: TC.VERSION_NOT_SYNCED 203. ERROR MESSAGE: 'This Test Case has been associated. Create a new version to save modifications.' 204. 205. AUTOMATIC RETRY STRATEGY (IMPLEMENT THIS PATTERN): 206. When you receive TC.VERSION_NOT_SYNCED error, AUTOMATICALLY retry with version creation: 207. DO NOT ask user for confirmation - this is expected behavior for associated test cases 208. 209. 1. FIRST ATTEMPT (Normal Update): 210. - Try updating with isStepUpdated=true (for step changes) or without withVersion flag 211. - If error code is TC.VERSION_NOT_SYNCED, proceed to step 2 212. - If error is different, report the error to user 213. 214. 2. AUTOMATIC RETRY (Version Creation): 215. - Use the SAME tcID, tcVersionID, and steps array from first attempt 216. - Add these flags to payload: 217. * withVersion: true (CRITICAL - enables version creation) 218. * tcVersion: <current version number> (get from test case details or executions) 219. * notrunall: false (use false, not true) 220. * notruncurrent: false (use false, not true) 221. * scope: 'project' (always required) 222. * versionComment: 'Auto-created version due to test suite association' (or custom message) 223. - Set isStepUpdated: true whenever you modify steps (including when withVersion=true) 224. - IMPORTANT: Include ALL existing steps with tcStepID + new steps without tcStepID 225. 226. 3. VERIFICATION: 227. - Check response for new tcVersionID (will be different from source) 228. - Verify tcVersion incremented (e.g., 1→2, 2→3) 229. - Confirm success message: 'Test Case <entityKey> updated successfully' 230. 231. UI BEHAVIOR COMPARISON: 232. QMetry UI shows a popup: 'Save as new version?' with optional comment field 233. API equivalent: Automatic retry with withVersion=true after detecting TC.VERSION_NOT_SYNCED 234. 235. REAL-WORLD EXAMPLE FROM UI PAYLOADS: 236. 237. First Attempt (FAILS with TC.VERSION_NOT_SYNCED): 238. ```pseudo 239. { 240. "tcID": 4594140, 241. "tcVersionID": 5536696, 242. "withVersion": false, 243. "notrunall": false, 244. "steps": [ 245. // ... 5 existing steps with tcStepID ... 246. // ... 1 new step without tcStepID (orderId: 6) ... 247. ], 248. "removeSteps": [], 249. "isStepUpdated": true 250. } 251. ``` 252. Response: 400 - TC.VERSION_NOT_SYNCED error 253. 254. Second Attempt (SUCCEEDS - Creates Version 2): 255. ```pseudo 256. { 257. "withVersion": true, // NEW: Version creation flag 258. "notrunall": false, 259. "notruncurrent": false, 260. "steps": [ 261. // SAME steps array as first attempt 262. // ... 5 existing steps with tcStepID ... 263. // ... 1 new step without tcStepID ... 264. ], 265. "removeSteps": [], 266. "scope": "project", 267. "tcID": 4594140, // SAME tcID 268. "tcVersion": 1, // NEW: Current version number 269. "tcVersionID": 5536696, // SAME tcVersionID (source version) 270. "versionComment": "test", // NEW: Version comment (optional) 271. // NOTE: isStepUpdated field is NOT included when withVersion=true 272. } 273. ``` 274. Response: 200 - Success, new tcVersionID created (e.g., 5536697), tcVersion=2 275. 276. IMPLEMENTATION PSEUDO-CODE: 277. ```typescript 278. try { 279. // First attempt: Normal update 280. const response = await updateTestCase({ 281. tcID, tcVersionID, steps, isStepUpdated: true 282. }); 283. } catch (error) { 284. if (error.code === 'TC.VERSION_NOT_SYNCED') { 285. // Automatic retry with version creation 286. const testCaseDetails = await fetchTestCaseDetails(tcID); 287. // CRITICAL: Use the LATEST version number from system 288. const latestVersion = testCaseDetails.tcVersion; // e.g., 2 if v2 exists 289. const response = await updateTestCase({ 290. tcID, 291. tcVersionID, // Same source version 292. tcVersion: latestVersion, // Use latest version number (not always 1!) 293. steps, // Same steps array 294. // DO NOT include isStepUpdated when withVersion=true 295. withVersion: true, // Enable version creation 296. notrunall: false, // Use false (verified working value) 297. notruncurrent: false, // Use false (verified working value) 298. scope: 'project', // Always required 299. versionComment: 'Auto-created version due to test suite association' 300. }); 301. } else { 302. throw error; // Different error, report to user 303. } 304. } 305. ``` 306. 307. KEY INSIGHTS: 308. - DO NOT ask user for confirmation - auto-retry is expected behavior 309. - Use SAME tcVersionID in both attempts (source version for creation) 310. - Second attempt creates NEW version (tcVersionID changes in response) 311. - Steps array is IDENTICAL in both attempts 312. - tcVersion parameter is ONLY in second attempt (withVersion=true) 313. - This matches QMetry UI behavior where popup auto-triggers version creation 314. 315. CRITICAL: INCREMENTAL tcVersion SELECTION RULE 316. 317. PROBLEM: When multiple versions exist, which tcVersion should you use? 318. SOLUTION: Use the VERSION NUMBER of the version you are creating FROM (the latest existing version) 319. 320. RULE: When creating a new version, tcVersion must equal the CURRENT LATEST VERSION in the system 321. 322. EXAMPLES: 323. - If only version 1 exists: Use tcVersion: 1 (creates version 2 from v1) 324. - If version 1 and 2 exist: Use tcVersion: 2 (creates version 3 from v2) 325. - If version 1, 2, and 3 exist: Use tcVersion: 3 (creates version 4 from v3) 326. 327. WORKFLOW TO DETERMINE CORRECT tcVersion: 328. 1. Call FETCH_TEST_CASE_DETAILS or FETCH_TEST_CASE_EXECUTIONS 329. 2. Check the highest tcVersion number in the system 330. 3. Use that number as your tcVersion parameter in the update payload 331. 4. This ensures you're creating from the latest version, not an old one 332. 333. REAL-WORLD SCENARIO: 334. Scenario: Test case VKMCP-TC-43 has version 2 already created in UI 335. Wrong Approach (will fail): tcVersion: 1, withVersion: true → TC.VERSION_NOT_SYNCED error 336. Correct Approach (will succeed): tcVersion: 2, withVersion: true → Creates version 3 successfully 337. 338. VERIFIED WORKING PAYLOAD (from user's Postman testing): 339. ```json 340. { 341. "notrunall": false, 342. "notruncurrent": false, 343. "scope": "project", 344. "tcID": 4594145, 345. "tcVersion": 2, // KEY: Use version 2 because v2 already exists 346. "tcVersionID": 5536706, // Source version ID (stays same) 347. "versionComment": "Added new steps", // Describes what changed 348. "withVersion": true, // Enable version creation 349. "steps": [ 350. // 5 existing steps with tcStepID (preserved from source) 351. // 2 new steps without tcStepID (to be added) 352. ] 353. } 354. ``` 355. Result: New version 3 created successfully with 7 total steps 356. 357. DEFAULT VALUES FOR TC.VERSION_NOT_SYNCED RETRIES (THIS PATTERN): 358. - notrunall: false - For this retry pattern, override any usual `true` default 359. - notruncurrent: false - For this retry pattern, override any usual `true` default 360. - scope: "project" - Always use this 361. - withVersion: true - Required when creating a new version (both initial and retries) 362. 363. WHEN TO APPLY THIS PATTERN: 364. ✓ Adding steps to test case linked to test suite 365. ✓ Editing steps in test case with existing executions 366. ✓ Removing steps from associated test case 367. ✓ Any modification to steps when TC.VERSION_NOT_SYNCED occurs 368. ✓ When creating new versions from existing versions (always check latest version number) 369. 370. WHEN NOT TO APPLY: 371. ✗ Test case is NOT linked to test suite (normal update works) 372. ✗ Only updating metadata (name, priority, etc.) without steps 373. ✗ Different error codes (handle appropriately) 374. 375. BENEFITS OF THIS APPROACH: 376. 1. Seamless UX - LLM handles version creation automatically 377. 2. Matches UI behavior - no manual intervention needed 378. 3. Preserves test history - creates proper version trail 379. 4. Maintains test suite linkage - version creation preserves associations 380. 5. Handles incremental versions correctly - uses latest version as source 381. 382. 🎯 GRACEFUL HANDLING SUMMARY: 383. 384. When adding/editing/removing steps from test cases: 385. 1. Always TRY normal update first (without withVersion flag) 386. 2. If TC.VERSION_NOT_SYNCED error received: 387. - Fetch latest version number from test case details/executions 388. - Automatically retry with withVersion=true + correct tcVersion 389. - Use notrunall=false, notruncurrent=false, scope='project' 390. - Include version comment describing the changes 391. 3. Report success with new version details to user 392. 4. NEVER ask for confirmation - handle it transparently 393. 394. This ensures test cases with executions or suite associations are handled gracefully 395. without user intervention, matching the QMetry UI experience exactly. 396. 397. executionMinutes time is in minutes (legacy field). 398. estimatedTime is in seconds (preferred for version creation). 399. Description and testingType are optional but recommended for clarity. 400. 401. UDF (User Defined Fields) WORKFLOW FOR UPDATE: 402. 1. Call 'Fetch UDF Layout' with entityType='TC', pageName='DETAIL' to get field names, fieldIDs (projectUserFieldID), and list option IDs. 403. IF listOptions[field.listName] is empty after Fetch UDF Layout, the tool already tried a metadata fallback. If STILL empty, ask the user to provide the option ID from the QMetry UI — do NOT guess numeric IDs. 404. 2. For LOOKUPLIST fields: pick one ID from listOptions[field.listName][].id. 405. 3. For MULTILOOKUPLIST fields: pick an array of IDs; also pass the alias flat key (e.g., fieldNameAlias: 'Option Label'). 406. 4. For CASCADINGLIST fields: pick parent ID + fetch child with 'Fetch Cascade Child Values'. Pass { parent: parentId, child: childId }. 407. 5. Pass BOTH 'udfFields' (flat root values) AND 'UDF' wrapper (with fieldID) — both required for update. 408. Example: udfFields: { custom_text: 'new value' }, UDF: { custom_text: { fieldID: 1001, value: 'new value' } } 409. 6. Mandatory UDF fields (isMandatory=true) MUST be included. 410. STEP UDFs for update: Use same step UDF field names from 'Fetch UDF Layout' stepFields. Pass in each step's 'UDF' object. 411. For MULTILOOKUPLIST step UDFs in update: use { ADD: [id1, id2], REMOVE: [id3] } format.
- CurrentUpdate an existing QMetry test case OR create a new version by tcID and tcVersionID, with auto-resolution from entityKey. **Toolset:** Test Cases **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - tcID (number) *required*: Test Case numeric ID. CRITICAL: the parameter name is 'tcID' — do NOT use 'testCaseId', 'testCaseID', 'tcId', or other variants. Accepts a string or number. This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results or by using filters. - tcVersionID (number) *required*: Test Case version number. This is the internal numeric identifier for the version. - tcVersion (number): Test Case version number (required when withVersion=true for creating new version). This is the current version number from which a new version will be created. - withVersion (boolean): Pass 'true' if you want to create a new version of the test case with incremented version number. When true, a new version is created (e.g., if current version is 2, new version 3 is created). When false or omitted, updates the existing version specified by tcVersionID. IMPORTANT: Always send proper tcVersionID to identify which version the request is for. - versionComment (string): Comment or description for the new version (used only when withVersion=true). Helps track what changed in this new version. Example: 'Updated test steps for new requirements' - notruncurrent (boolean): Flag to control execution behavior for current version when creating a new version. Used in conjunction with withVersion=true. - notrunall (boolean): Flag to control execution behavior for all versions when creating a new version. Used in conjunction with withVersion=true. - folderPath (string): Folder path for test suites - SYSTEM AUTOMATICALLY SETS TO ROOT. Leave empty unless you want specific folder. System will automatically use empty string "" (root directory). Only specify if user wants specific folder like "Automation/Regression". (default: "") - scope (string): Scope of the operation - defines the context for data retrieval. Common values: 'project' (default), 'folder', 'release', 'cycle'. Applies to any entity type being fetched or operated upon. (default: "project") - isStepUpdated (boolean): Set to true when steps are being added, updated, or removed. Required when including 'steps' or 'removeSteps' arrays. - steps (array) - removeSteps (array) - name (string) - priority (number) - component (array) - testcaseOwner (number) - testCaseState (number) - testCaseType (number) - estimatedTime (number): Estimated execution time in seconds. Example: 7200 for 2 hours - executionMinutes (number) - testingType (number) - description (string) - updateOnlyMetadata (boolean): Set to true to update only metadata fields without touching test steps. When true, steps and removeSteps are ignored. - udfFields (record<string, union>): Flat UDF field values. Keys = UDF field names from 'Fetch UDF Layout'. Values depend on fieldTypeName: STRING/LARGETEXT: string, NUMBER: number, DATETIMEPICKER: date string ('14-08-2026'), LOOKUPLIST: numeric ID, MULTILOOKUPLIST: array of IDs [101, 102], CASCADINGLIST: { parent: 101, child: 102 }. Call 'Fetch UDF Layout' with entityType + pageName='ADD' to discover available fields and list option IDs. - UDF (record<string, object>): UDF wrapper required for update operations. Keys = UDF field names. Each value must include fieldID (from 'Fetch UDF Layout' with pageName='DETAIL') and value. Also set matching flat key in udfFields for the LOOKUPLIST Alias display. Example: { custom_text: { fieldID: 1001, value: 'new value' } } **Output Description:** JSON object containing the test case ID, version ID, summary, update/creation metadata. When withVersion=true (version creation), response includes new version number and version ID. When withVersion=false/omitted (existing version update), response includes updated fields confirmation. **Use Cases:** 1. Update test case summary (name) 2. Change priority, owner, or state of a test case 3. Edit, add, or remove test steps 4. Update only metadata (no steps) 5. Create a new version of a test case (withVersion=true) 6. Update a specific version of a test case (without withVersion flag) 7. Bulk update using entityKey auto-resolution 8. Modify test case description or estimated time 9. Change test case type or component 10. Update testing type or custom fields 11. Update, add and remove test case steps 12. Version control for test case evolution tracking **Examples:** 1. Update test case summary (existing version update) ```json { "tcID": 4519260, "tcVersionID": 5448492, "name": "MAC Test11" } ``` Expected Output: Test case summary updated. tcID and tcVersionID auto-resolved from entityKey. Only 'name' field changed. Version remains the same. 2. Create NEW VERSION with updated summary and description ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Add two numbers 2 v2", "description": "Test Description version 2", "withVersion": true, "versionComment": "version 2 comment add", "notruncurrent": true, "notrunall": true } ``` Expected Output: New version created (version 2). Test case now has incremental version with updated summary and description. Original version 1 remains unchanged. 3. Create NEW VERSION with all metadata fields (release, cycle, priority, owner, etc.) ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Facebook Login Validation Failed update from MCP V2", "description": "Existing description V2", "priority": 2355751, "testcaseOwner": 6963, "testCaseState": 2355753, "testCaseType": 2355762, "estimatedTime": 7200, "withVersion": true, "versionComment": "Created version 2 with updated metadata", "notruncurrent": true, "notrunall": true, "folderPath": 602290, "scope": "project" } ``` Expected Output: New test case version 2 created with updated summary, description, priority (High), owner (umang.savaliya), state, type, and estimated time (2 hours). Version comment added for tracking. 4. Update EXISTING VERSION 2 (not creating new version) ```json { "tcID": 4572654, "tcVersionID": 5514385, "name": "Updated version 2 name", "priority": 2355752 } ``` Expected Output: Version 2 updated with new name and priority. No new version created because withVersion flag is not set. This is a normal update of existing version. 5. Update priority to High and owner to john.doe (existing version) ```json { "tcID": 4519260, "tcVersionID": 5448492, "priority": 505015, "testcaseOwner": 6963 } ``` Expected Output: Priority and owner updated. Field IDs auto-resolved from project info. tcID/tcVersionID resolved from entityKey. Existing version modified. 6. Update steps (edit, add, remove) - existing version ```json { "tcID": 4519260, "tcVersionID": 5448492, "steps": [ { "orderId": 1, "description": "Step 22", "inputData": "Input 22", "expectedOutcome": "Outcome 22", "tcStepID": 3014032 }, { "orderId": 2, "description": "Step3", "inputData": "Input 3", "expectedOutcome": "Outcome 3" } ], "removeSteps": [ { "tcStepID": 3014031, "description": "Step 1", "orderId": 1 } ], "isStepUpdated": true } ``` Expected Output: Steps updated: Step 22 edited (tcStepID preserved), Step3 added (no tcStepID), Step 1 removed. tcID/tcVersionID auto-resolved. Existing version modified. 7. Create NEW VERSION with updated steps ```json { "tcID": 4572654, "tcVersionID": 5514384, "tcVersion": 1, "name": "Add two numbers 2 v2", "steps": [ { "orderId": 1, "description": "I and u have a calculator", "inputData": "", "expectedOutcome": "", "tcStepID": 38001791 }, { "orderId": 2, "description": "I add 41 and 31", "inputData": "", "expectedOutcome": "", "tcStepID": 38001793 }, { "orderId": 3, "description": "the result should be 72", "inputData": "", "expectedOutcome": "", "tcStepID": 38001792 } ], "withVersion": true, "versionComment": "version 2 with preserved steps", "notruncurrent": true, "notrunall": true, "isStepUpdated": true } ``` Expected Output: New version 2 created with all steps from version 1 preserved. Steps carry forward with their tcStepID values. Version comment added for tracking. 8. Update only metadata (no steps) - existing version ```json { "tcID": 4519260, "tcVersionID": 5448492, "updateOnlyMetadata": true, "name": "New Name" } ``` Expected Output: Metadata updated only. Steps unchanged. tcID/tcVersionID auto-resolved. Existing version modified. 9. Create NEW VERSION from existing version 2 with updated steps (working payload for linked test cases) ```json { "tcID": 4594145, "tcVersionID": 5536706, "tcVersion": 2, "name": "Mock Test Case - E-commerce Checkout Flow - v3", "steps": [ { "orderId": 1, "description": "Open browser and navigate to e-commerce website", "expectedOutcome": "Homepage loads successfully with product catalog", "inputData": "URL: https://example-shop.com", "tcStepID": 38129471 }, { "orderId": 2, "description": "Search for product", "expectedOutcome": "Search results display relevant products", "inputData": "Search term: 'wireless headphones'", "tcStepID": 38129475 }, { "orderId": 3, "description": "Select product and add to cart", "expectedOutcome": "Product added to cart, cart counter increments", "inputData": "Click 'Add to Cart' button", "tcStepID": 38129472 }, { "orderId": 4, "description": "Proceed to checkout", "expectedOutcome": "Checkout page displays with cart summary", "inputData": "Click cart icon and 'Proceed to Checkout'", "tcStepID": 38129473 }, { "orderId": 5, "description": "Complete payment", "expectedOutcome": "Order confirmation page displayed", "inputData": "Fill payment details and submit", "tcStepID": 38129474 }, { "orderId": 6, "description": "Verify order confirmation email received", "expectedOutcome": "Email with order details received in inbox", "inputData": "Check email account for confirmation" }, { "orderId": 7, "description": "Check order status in account dashboard", "expectedOutcome": "Order status shows as 'Processing' with tracking information", "inputData": "Navigate to My Orders section" } ], "withVersion": true, "versionComment": "Created version 3: Added 2 new verification steps (email and order status check)", "notrunall": false, "notruncurrent": false, "scope": "project" } ``` Expected Output: New version 3 created successfully from version 2. Test case now has 7 steps (5 preserved + 2 new). Key: tcVersion=2 was used because version 2 already existed in system. notrunall and notruncurrent both false (not true). Result shows tcVersion: 3 in response with new tcVersionID. **Hints:** 1. === DEFAULT VALUES — APPLY FOR ANY UNSET FIELD === 2. Call 'Fetch UDF Layout' with entityType='TC', pageName='DETAIL' before updating. 3. defaultValues (from Fetch UDF Layout): { fieldName: defaultValueId } — sweep ALL entries. 4. For EACH key in defaultValues: if user did not explicitly provide that field → include it in payload with the default value. 5. This applies to non-mandatory fields too (e.g. priority, estimatedTime). Omitting them = data loss. 6. === END DEFAULT VALUES === 7. 8. === DATE FORMAT CHECK (MANDATORY — EVERY UPDATE REQUEST) === 9. ALWAYS call 'Fetch QMetry Project Info' before every update request — not only when the user explicitly mentions a date. 10. Any UDF field could be a DATETIMEPICKER. Wrong format causes QMetry to silently discard the field value (API returns success but value is NOT stored — no error). 11. STEP 1: From project info, read dateTimeFormatID (e.g. 3). 12. STEP 2: Find entry in dateTimeFormatNew where id === dateTimeFormatID → read its unique_value (e.g. 'yyyy-MM-dd'). 13. STEP 3: unique_value pattern: yyyy=4-digit year, MM=2-digit month (01-12), dd=2-digit day, MMM=3-letter month (Jan/Feb/...). 14. Example: id=1 → MM-dd-yyyy → '10-25-2000' | id=2 → dd-MM-yyyy → '25-10-2000' | id=3 → yyyy-MM-dd → '2000-10-25' | id=4 → dd-MMM-yyyy → '25-Oct-2000' 15. STEP 4: For EVERY DATETIMEPICKER field in the payload: parse any user-provided date and re-format it using the active unique_value pattern before sending. 16. NEVER assume a date format — always derive it from dateTimeFormatID. Wrong format = silent data loss. 17. === END DATE FORMAT CHECK === 18. 19. CRITICAL - VERSION CREATION vs UPDATE DISTINCTION: 20. This tool supports TWO MODES using the SAME API endpoint: 21. 22. MODE 1: CREATE NEW VERSION (withVersion=true) 23. - Purpose: Create an incremental version of the test case (e.g., v1 → v2, v2 → v3) 24. - When to use: User explicitly asks to 'create new version', 'create version 2', 'increment version' 25. - Required fields: tcID, tcVersionID (of source version), tcVersion (current version number), withVersion=true 26. - Optional but recommended: versionComment (track what changed), notruncurrent, notrunall 27. - Behavior: Creates a NEW test case version with incremented version number. Source version remains unchanged. 28. - Example: If current version is 1, setting withVersion=true creates version 2 29. - Use cases: Updating test case for new requirements, creating variants for different scenarios, version control 30. 31. MODE 2: UPDATE EXISTING VERSION (withVersion=false or omitted) 32. - Purpose: Modify fields of an EXISTING version without creating a new version 33. - When to use: User asks to 'update test case', 'modify version X', 'change summary' (without mentioning new version) 34. - Required fields: tcID, tcVersionID (of version to update) 35. - Do NOT include: withVersion flag, versionComment, tcVersion 36. - Behavior: Updates the specified version in-place. No new version is created. 37. - Example: Updating version 2's summary - only version 2 is modified, no version 3 is created 38. - Use cases: Fixing typos, updating metadata, modifying steps in existing version 39. 40. CRITICAL FIELD UNDERSTANDING: 41. - tcVersionID: The VERSION ID (numeric identifier) of the version you're working with 42. - tcVersion: The VERSION NUMBER (1, 2, 3, etc.) - only needed when withVersion=true 43. - tcID: The TEST CASE ID (remains same across all versions) 44. - Example: Test case VKMCP-TC-10 (tcID: 4572654) has version 1 (tcVersionID: 5514384, tcVersion: 1) 45. - When creating version 2 from version 1: Send tcVersionID=5514384 (source), tcVersion=1 (current), withVersion=true 46. 47. HOW TO DETERMINE WHICH MODE: 48. 'create new version' / 'create version 2' / 'update with new version' → MODE 1 (withVersion=true) 49. 'update test case' / 'change priority' / 'modify version X' (no mention of new version) → MODE 2 50. Ambiguous → ask: 'Do you want to create a new version or update the existing version?' 51. 52. VERSION CREATION WORKFLOW: fetch tcID + latest tcVersionID + tcVersion → build payload → call API. 53. New version inherits all source fields; only explicitly passed fields are overridden. 54. Recommended: include versionComment. Steps: use tcStepID to preserve, omit to add, use removeSteps to delete. 55. Set isStepUpdated:true if steps are added, modified, or removed. 56. 57. FIELD IDs for version creation — all from project info customListObjs.<field>[].id: 58. priority | testcaseOwner (→owner list) | testCaseState | testCaseType | testingType | component (array of IDs) 59. estimatedTime in seconds | scope:'project' | folderPath: string path or numeric ID 60. 61. If user provides entityKey (e.g., MAC-TC-1684), first call FETCH_TEST_CASES with a filter on entityKeyId to resolve the tcID and tcVersionID. 62. To get valid values for priority, owner, component, etc., call the project info tool and use the returned customListObjs IDs. 63. NAMED FIELD RESOLUTION (priority, component, owner, testCaseState, testCaseType, testingType): 64. If user provides a name instead of an ID: look up ID from project info customListObjs.<field>[].name. 65. Field→key map: priority→priority | component→component | owner→testcaseOwner | state→testCaseState | type→testCaseType | testingType→testingType. 66. If not found after a fresh project info fetch: skip the field (it is not required) and show: 67. 'Test case updated without <field>, as given <field> is not available in the current project.' 68. 69. CRITICAL: To update test case steps without **Duplication**, use the following rules: 70. - ANTI-DUPLICATION RULE: The tcStepID field is THE KEY to prevent duplication: 71. * WITH tcStepID = UPDATE existing step (QMetry modifies the existing step in place) 72. * WITHOUT tcStepID = CREATE new step (QMetry adds a brand new step) 73. - For steps to be UPDATED: ALWAYS fetch existing steps first using FETCH_TEST_CASE_STEPS, then include the tcStepID in the step object. 74. - For steps to be ADDED: omit tcStepID completely in the step object. 75. - For steps to be REMOVED: add a full removeSteps object for each step to be deleted, matching the removeTestCaseStep interface. 76. - CRITICAL WARNING - DO NOT ADD UNSOLICITED STEPS: 77. * ONLY add, edit, or remove steps that the user EXPLICITLY requested 78. * DO NOT invent, create, or add extra steps based on assumptions or best practices 79. * DO NOT add 'helpful' steps that the user did not ask for 80. * When user says 'remove step 1', the result should have (N-1) steps, not N steps with extras 81. * When user says 'add 1 step', ONLY add that 1 step, nothing more 82. * When user says 'update step 2', ONLY update step 2, do not add or modify other steps 83. * If unsure what user wants, ASK first rather than adding steps autonomously 84. - WORKFLOW TO AVOID DUPLICATION: 85. 1. Call FETCH_TEST_CASE_STEPS to get all existing steps with their tcStepID values 86. 2. For steps you want to KEEP/UPDATE: Include them in steps[] WITH their original tcStepID 87. 3. For steps you want to ADD: Include them in steps[] WITHOUT tcStepID (ONLY if user requested) 88. 4. For steps you want to REMOVE: Include them in removeSteps[] with full details 89. 5. Always set isStepUpdated: true if steps are added, updated, or removed 90. 6. VERIFY your steps array matches user's explicit request (count and content) 91. - Example: If user says 'Edit step 1 to say ...', FIRST fetch steps to get tcStepID for step 1, THEN include it in the steps array with updated fields and the ORIGINAL tcStepID. 92. - Example: If user says 'Add a new step after step 2', add EXACTLY ONE new object to steps array with no tcStepID (not multiple steps). 93. - Example: If user says 'Remove step 3', add the full step object to removeSteps array, including tcStepID and all required fields. Do NOT add replacement steps. 94. - Example: If test case has 3 steps and user says 'remove step 1', result should have 2 steps (step 2 and step 3 with updated orderIds), NOT 3 steps with extras. 95. - Example: If user says 'add one mock step', add EXACTLY ONE step (not 2 or 3 steps even if they seem related). 96. - COMPLETE PAYLOAD EXAMPLE: { tcID: 123, tcVersionID: 456, steps: [{tcStepID: 1001, orderId: 1, description: 'Updated'}, {orderId: 2, description: 'New'}], removeSteps: [{tcStepID: 1002, orderId: 3, ...}], isStepUpdated: true } 97. - If only metadata is updated (no steps), set updateOnlyMetadata: true and do not include steps/removeSteps. 98. - Always preserve orderId sequence for proper step ordering. 99. - If user prompt is ambiguous, ask for clarification or show a user-friendly error. 100. - WARNING: Omitting tcStepID for existing steps will cause DUPLICATION - the API will create duplicates instead of updating! 101. - FINAL VERIFICATION BEFORE SENDING REQUEST: 102. * Count steps in your payload vs what user requested 103. * If user said 'add 1 step', steps array should have (existing_count + 1) items total 104. * If user said 'remove 1 step', steps array should have (existing_count - 1) items total, removeSteps should have 1 item 105. * If user said 'update step X', steps array should have same count as before, with step X's tcStepID preserved 106. * NEVER include steps the user did not explicitly mention or request 107. Steps are optional but recommended for manual test cases. 108. If the user provides a prompt like 'update test case with steps as step 1 - Go to login page, step 2 - give credential, step 3 - go to test case page, step 4 - create test case', LLM should parse each step and convert it into the steps payload array, mapping each step to an object with orderId, description, and optionally inputData and expectedOutcome. 109. Example mapping: 'step 1 - Go to login page' → { orderId: 1, description: 'Go to login page' }. 110. LLM should increment orderId for each step, use the step text as description, and optionally infer inputData/expectedOutcome if provided in the prompt. 111. Demo steps payload: steps: [ { orderId: 1, description: 'First Step', inputData: 'First Data', expectedOutcome: 'First Outcome', UDF: { customField1: 'Custom Field Data A', customField2: 'Custom Field Data B' } }, ... ] 112. UDF fields in steps must match your QMetry custom field configuration. 113. All IDs (priority, owner, etc.) must be valid for your QMetry instance. 114. If a custom field is mandatory, include it in the UDF object. 115. 116. VERSION CREATION NOTES: 117. - notruncurrent + notrunall: default true for regular version creation; use false only in TC.VERSION_NOT_SYNCED retry. 118. - folderPath: string path or numeric ID; inherited from source version if omitted. 119. - attachments: use ADD/REMOVE arrays to manage attachments on create or update. 120. 121. PITFALL: tcVersionID (numeric version identifier, stays same across creation) ≠ tcVersion (version number 1/2/3, only used when withVersion=true). 122. 123. TC.VERSION_NOT_SYNCED — AUTO-RETRY (transparent, no user confirmation needed): 124. TRIGGER: Test case linked to test suites or has existing executions — direct step updates are blocked. 125. ERROR CODE: TC.VERSION_NOT_SYNCED | MESSAGE: 'This Test Case has been associated. Create a new version to save modifications.' 126. 127. RETRY FLOW: 128. 1. First attempt — normal update (no withVersion). If TC.VERSION_NOT_SYNCED → go to step 2. Different error → report and stop. 129. 2. Fetch test case details to get LATEST tcVersion number. 130. CRITICAL: use the highest existing version (e.g. v2 exists → tcVersion=2, not 1). Wrong value triggers the error again. 131. 3. Retry with SAME tcID, tcVersionID, steps[] PLUS these additional fields: 132. withVersion: true | tcVersion: <latest> | notrunall: false | notruncurrent: false | scope: 'project' 133. versionComment: 'Auto-created version due to test suite association' 134. NOTE: omit isStepUpdated when withVersion=true. 135. 4. Verify new tcVersionID in response (different from source) and report new version details to user. 136. 137. tcVersion RULE: always equals the LATEST version in the system. 138. Only v1 exists → tcVersion:1 (creates v2) | v1+v2 exist → tcVersion:2 (creates v3) | etc. 139. 140. VERIFIED PAYLOAD SHAPE (retry attempt): 141. { tcID, tcVersionID, tcVersion:<latest>, withVersion:true, notrunall:false, notruncurrent:false, 142. scope:'project', versionComment:'...', steps:[...same as first attempt...] } 143. 144. executionMinutes time is in minutes (legacy field). 145. estimatedTime is in seconds (preferred for version creation). 146. Description and testingType are optional but recommended for clarity. 147. 148. UDF (User Defined Fields) WORKFLOW FOR UPDATE: 149. 1. Call 'Fetch UDF Layout' with entityType='TC', pageName='DETAIL' to get field names, fieldIDs (projectUserFieldID), and list option IDs. 150. IF listOptions[field.listName] is empty after Fetch UDF Layout, the tool already tried a metadata fallback. If STILL empty, ask the user to provide the option ID from the QMetry UI — do NOT guess numeric IDs. 151. 2. For LOOKUPLIST fields: pick one ID from listOptions[field.listName][].id. 152. 3. For MULTILOOKUPLIST fields: pick an array of IDs; also pass the alias flat key (e.g., fieldNameAlias: 'Option Label'). 153. 4. For CASCADINGLIST fields: pick parent ID + fetch child with 'Fetch Cascade Child Values'. Pass { parent: parentId, child: childId }. 154. 5. Pass BOTH 'udfFields' (flat root values) AND 'UDF' wrapper (with fieldID) — both required for update. 155. Example: udfFields: { custom_text: 'new value' }, UDF: { custom_text: { fieldID: 1001, value: 'new value' } } 156. 6. Mandatory UDF fields (isMandatory=true) MUST be included. 157. STEP UDFs for update: Use same step UDF field names from 'Fetch UDF Layout' stepFields. Pass in each step's 'UDF' object. 158. For MULTILOOKUPLIST step UDFs in update: use { ADD: [id1, id2], REMOVE: [id3] } format.
Input schema
Property Previous (0.42.0) Current (0.43.0) Change ownernumberoptional not present - Removed
testcaseOwnernot present numberoptional - Added
48 unchanged entries
(schema root)UDFcomponentcomponent › [items]descriptionestimatedTimeexecutionMinutesfolderPathisStepUpdatednamenotrunallnotruncurrentpriorityprojectKeyremoveStepsremoveSteps › [items]removeSteps › [items] › UDFremoveSteps › [items] › descriptionremoveSteps › [items] › expectedOutcomeremoveSteps › [items] › inputDataremoveSteps › [items] › orderIdremoveSteps › [items] › projectIDremoveSteps › [items] › tcIDremoveSteps › [items] › tcStepIDremoveSteps › [items] › tcVersionremoveSteps › [items] › tcVersionIDremoveSteps › [items] › tcsAttCountremoveSteps › [items] › tcsIsParameterizedremoveSteps › [items] › tcsIsSharedscopestepssteps › [items]steps › [items] › UDFsteps › [items] › descriptionsteps › [items] › expectedOutcomesteps › [items] › inputDatasteps › [items] › orderIdsteps › [items] › tcStepIDtcIDtcVersiontcVersionIDtestCaseStatetestCaseTypetestingTypeudfFieldsupdateOnlyMetadataversionCommentwithVersion
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
swagger_create_portal_productModifiedWhat changed
- swagger_create_portal_product — Schema change: input property added: visibility.
- swagger_create_portal_product — Schema change: input property removed: hidden.
- swagger_create_portal_product — Output schema: property added: visibility.
- swagger_create_portal_product — Output schema: property removed: hidden.
- swagger_create_portal_product: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousCreate a new product for a specific portal. **Toolset:** Products **Parameters:** - portalId (string) *required*: Portal UUID or subdomain - unique identifier for the portal instance - type (string) *required*: Product creation type - 'new' to create from scratch or 'copy' to duplicate an existing product - productId (string): Source product UUID to copy from - required when type is 'copy', specifies which existing product to duplicate. Omit when type is 'new' - name (string) *required*: Product display name - will be shown to users in the portal navigation and product listings (3-40 characters) - slug (string) *required*: URL-friendly identifier for the product - must be unique within the portal, used in URLs (e.g., 'my-api' becomes /my-api). 3-22 characters, lowercase, alphanumeric with hyphens, underscores, or dots - description (string): Product description - explains what the API/product does, shown in product listings and cards (max 110 characters) - public (boolean): Whether the product is publicly visible to all portal visitors - false means only authenticated users with appropriate roles can access it - hidden (boolean): Whether the product is hidden from the portal landing page navigation menus - useful for internal or draft products
- CurrentCreate a new product for a specific portal. **Toolset:** Products **Parameters:** - portalId (string) *required*: Portal UUID or subdomain - unique identifier for the portal instance - type (string) *required*: Product creation type - 'new' to create from scratch or 'copy' to duplicate an existing product - productId (string): Source product UUID to copy from - required when type is 'copy', specifies which existing product to duplicate. Omit when type is 'new' - name (string) *required*: Product display name - will be shown to users in the portal navigation and product listings (3-40 characters) - slug (string) *required*: URL-friendly identifier for the product - must be unique within the portal, used in URLs (e.g., 'my-api' becomes /my-api). 3-22 characters, lowercase, alphanumeric with hyphens, underscores, or dots - description (string): Product description - explains what the API/product does, shown in product listings and cards (max 110 characters) - public (boolean): Whether the product is publicly visible to all portal visitors - false means only authenticated users with appropriate roles can access it - visibility (enum): Whether the product is shown on the portal landing page - 'visible' shows it to everyone, 'hidden' hides it from everyone, 'conditional' shows it only to users who have access to the product (not allowed when the product is public)
Input schema
Property Previous (0.42.0) Current (0.43.0) Change hiddenbooleanoptional not present - Removed
visibilitynot present string, enum (3)optional - Added
8 unchanged entries
(schema root)descriptionnameportalIdproductIdpublicslugtype
Output schema
Property Previous (0.42.0) Current (0.43.0) Change hiddenbooleanoptional not present - Removed
visibilitynot present string, enum (3)optional - Added
8 unchanged entries
(schema root)descriptionidnameportalIdpublicslugurl
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
swagger_get_portal_productModifiedWhat changed
- swagger_get_portal_product — Output schema: property added: visibility.
- swagger_get_portal_product — Output schema: property removed: hidden.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)productId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change hiddenbooleanoptional not present - Removed
visibilitynot present string, enum (3)optional - Added
8 unchanged entries
(schema root)descriptionidnameportalIdpublicslugurl
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
swagger_list_portal_productsModifiedWhat changed
- swagger_list_portal_products — Output schema: property items changed: items {"additionalPropert… → {"additionalPropert….
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)portalId
Output schema
Property Previous (0.42.0) Current (0.43.0) Change items › [items] › hiddenbooleanoptional not present - Removed
items › [items] › visibilitynot present string, enum (3)optional - Added
15 unchanged entries
(schema root)itemsitems › [items]items › [items] › descriptionitems › [items] › iditems › [items] › nameitems › [items] › portalIditems › [items] › publicitems › [items] › slugitems › [items] › urlpagepage › numberpage › sizepage › totalElementspage › totalPages
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
swagger_update_portal_productModifiedWhat changed
- swagger_update_portal_product — Schema change: input property added: visibility.
- swagger_update_portal_product — Schema change: input property removed: hidden.
- swagger_update_portal_product — Output schema: property added: visibility.
- swagger_update_portal_product — Output schema: property removed: hidden.
- swagger_update_portal_product: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate a product's settings within a specific portal. **Toolset:** Products **Parameters:** - productId (string) *required*: Product UUID or identifier in the format 'portal-subdomain:product-slug' - unique identifier for the product - name (string): Update product display name - changes how it appears to users in navigation and listings (3-40 characters) - slug (string): Update URL-friendly identifier - must remain unique within the portal, affects product URLs (3-22 characters, lowercase, alphanumeric with hyphens/underscores/dots) - description (string): Update product description - explains the API/product functionality, shown in listings (max 110 characters) - public (boolean): Change product visibility - true makes it publicly accessible to all visitors, false restricts to authenticated users with roles - hidden (boolean): Change navigation visibility - true hides from portal landing page menus while keeping the product accessible via direct links
- CurrentUpdate a product's settings within a specific portal. **Toolset:** Products **Parameters:** - productId (string) *required*: Product UUID or identifier in the format 'portal-subdomain:product-slug' - unique identifier for the product - name (string): Update product display name - changes how it appears to users in navigation and listings (3-40 characters) - slug (string): Update URL-friendly identifier - must remain unique within the portal, affects product URLs (3-22 characters, lowercase, alphanumeric with hyphens/underscores/dots) - description (string): Update product description - explains the API/product functionality, shown in listings (max 110 characters) - public (boolean): Change product visibility - true makes it publicly accessible to all visitors, false restricts to authenticated users with roles - visibility (enum): Change whether the product is shown on the portal landing page - 'visible' shows it to everyone, 'hidden' hides it from everyone, 'conditional' shows it only to users who have access to the product. Not allowed when the product is public; making a 'conditional' product public without also changing visibility fails with 409
Input schema
Property Previous (0.42.0) Current (0.43.0) Change hiddenbooleanoptional not present - Removed
visibilitynot present string, enum (3)optional - Added
6 unchanged entries
(schema root)descriptionnameproductIdpublicslug
Output schema
Property Previous (0.42.0) Current (0.43.0) Change hiddenbooleanoptional not present - Removed
visibilitynot present string, enum (3)optional - Added
8 unchanged entries
(schema root)descriptionidnameportalIdpublicslugurl
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
swagger_validate_apiModifiedWhat changed
- swagger_validate_api — Output schema: property findings changed: items {"additionalPropert… → {"additionalPropert….
- swagger_validate_api — Output schema: property summary changed: properties {"durationMs":{"typ… → {"durationMs":{"typ….
- swagger_validate_api: description changed.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousValidate an OpenAPI or AsyncAPI definition using server-side apidom-ls. Returns structured diagnostics with line number, severity, and message for each finding. Supports OpenAPI 2.0, 3.0, 3.1, and AsyncAPI. Provide either the raw definition (JSON or YAML) OR an existing API by owner, apiName, and version. Use this tool when the user asks to validate, lint, or check an API spec for structural errors matching the Studio Validation tab. **Toolset:** Registry API **Parameters:** - definition (string): API definition content (OpenAPI/AsyncAPI in JSON or YAML). Provide this or owner/apiName/version, not both. - owner (string): API owner (organization or user). Use with apiName and version to fetch an existing API from the registry. - apiName (string): API name - version (string): Version identifier - maxProblems (number): Cap on the number of findings returned (default 100, max 1000) - uri (string): Optional pseudo-URI hint for the parser (e.g. inmemory://spec.yaml)
- CurrentValidate an OpenAPI or AsyncAPI definition using server-side apidom-ls and asyncapi/parser. Returns structured diagnostics with line number, severity, and message for each finding. Supports OpenAPI 2.0, 3.0, 3.1, and AsyncAPI. Provide either the raw definition (JSON or YAML) OR an existing API by owner, apiName, and version. Use this tool when the user asks to validate, lint, or check an API spec for structural errors matching the Studio Validation tab. **Toolset:** Registry API **Parameters:** - definition (string): API definition content (OpenAPI/AsyncAPI in JSON or YAML). Provide this or owner/apiName/version, not both. - owner (string): API owner (organization or user). Use with apiName and version to fetch an existing API from the registry. - apiName (string): API name - version (string): Version identifier - maxProblems (number): Cap on the number of findings returned (default 100, max 1000) - uri (string): Optional pseudo-URI hint for the parser (e.g. inmemory://spec.yaml)
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)apiNamedefinitionmaxProblemsowneruriversion
Output schema
Property Previous (0.42.0) Current (0.43.0) Change findings › [items] › columnnumberoptional numberoptional - Description changed
findings › [items] › severitystring, enum (3)required string, enum (5)required - Constraint: enum
enum: ["error","warning","info"] → ["error","warning","information","hint","unknown"]findings › [items] › sourcestringoptional stringoptional - Description changed
summary › infonumberoptional not present - Removed
18 unchanged entries
(schema root)findingsfindings › [items]findings › [items] › codefindings › [items] › linefindings › [items] › messagerecognizedspecspec › formatspec › mediaTypespec › namespacespec › versionsummarysummary › durationMssummary › errorssummary › totalsummary › warningsvalid
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
195 tools with no recorded change
bearq_chat_with_qa_leadbearq_delete_test_casesbearq_expand_application_modelbearq_get_taskbearq_get_task_statusbearq_list_environmentsbearq_run_regression_testsbearq_run_test_casesbearq_run_tests_in_functional_areasbearq_wait_for_taskbugsnag_get_buildbugsnag_get_current_projectbugsnag_get_errorbugsnag_get_eventbugsnag_get_event_details_from_dashboard_urlbugsnag_get_events_on_an_errorbugsnag_get_network_endpoint_groupingsbugsnag_get_releasebugsnag_get_span_groupbugsnag_get_tracebugsnag_list_project_errorsbugsnag_list_project_event_filtersbugsnag_list_projectsbugsnag_list_releasesbugsnag_list_span_groupsbugsnag_list_spansbugsnag_list_trace_fieldsbugsnag_set_network_endpoint_groupingsbugsnag_update_errorcollaborator_create_remote_system_configurationcollaborator_create_reviewcollaborator_delete_remote_system_configurationcollaborator_edit_remote_system_configurationcollaborator_find_review_by_idcollaborator_get_reviewscollaborator_reject_reviewcollaborator_reviewservice_actioncollaborator_test_remote_system_configuration_connectioncollaborator_update_remote_system_configuration_webhookqmetry_bulk_update_test_run_udfsqmetry_create_cycleqmetry_create_defect_or_issueqmetry_create_releaseqmetry_create_requirementqmetry_create_test_caseqmetry_create_test_suiteqmetry_export_html_reportqmetry_fetch_automation_statusqmetry_fetch_buildsqmetry_fetch_cascade_child_valuesqmetry_fetch_defects_or_issuesqmetry_fetch_issue_detailsqmetry_fetch_issue_executionsqmetry_fetch_issues_linked_to_test_caseqmetry_fetch_linked_issues_of_test_case_runqmetry_fetch_platformsqmetry_fetch_qmetry_list_projectsqmetry_fetch_qmetry_project_infoqmetry_fetch_quality_gate_configurationqmetry_fetch_releases_and_cyclesqmetry_fetch_requirement_detailsqmetry_fetch_requirementsqmetry_fetch_requirements_linked_to_test_caseqmetry_fetch_test_case_detailsqmetry_fetch_test_case_executionsqmetry_fetch_test_case_stepsqmetry_fetch_test_case_steps_with_udfqmetry_fetch_test_case_version_detailsqmetry_fetch_test_casesqmetry_fetch_test_cases_linked_to_requirementqmetry_fetch_test_cases_linked_to_test_suiteqmetry_fetch_test_run_udf_metadataqmetry_fetch_test_run_udf_valuesqmetry_fetch_test_suite_detailsqmetry_fetch_test_suitesqmetry_fetch_test_suites_for_test_caseqmetry_fetch_udf_layoutqmetry_import_automation_test_resultsqmetry_link_issues_to_testcase_runqmetry_link_platforms_to_test_suiteqmetry_link_requirements_to_testcaseqmetry_link_test_case_to_issuesqmetry_link_test_cases_to_test_suiteqmetry_requirements_linked_test_cases_to_test_suiteqmetry_set_qmetry_project_infoqmetry_update_cycleqmetry_update_requirementqmetry_update_test_suiteqtm4j_create_test_caseqtm4j_create_test_cycleqtm4j_get_automation_historyqtm4j_get_linked_bugs_of_test_case_executionqtm4j_get_linked_bugs_of_test_step_executionqtm4j_get_linked_requirementsqtm4j_get_linked_requirements_for_test_cycleqtm4j_get_linked_test_cases_for_requirementqtm4j_get_projectsqtm4j_get_test_stepsqtm4j_link_bugs_to_test_case_executionqtm4j_link_bugs_to_test_step_executionqtm4j_link_requirements_to_test_caseqtm4j_link_requirements_to_test_cycleqtm4j_link_test_cases_to_requirementqtm4j_link_test_cases_to_test_cycleqtm4j_search_linked_test_cases_in_test_cycleqtm4j_search_test_casesqtm4j_search_test_cyclesqtm4j_set_project_contextqtm4j_start_new_executionqtm4j_unlink_requirements_from_test_caseqtm4j_unlink_requirements_from_test_cycleqtm4j_unlink_test_cases_from_requirementqtm4j_unlink_test_cases_from_test_cycleqtm4j_update_test_caseqtm4j_update_test_case_executionqtm4j_update_test_cycleqtm4j_update_test_step_executionqtm4j_upload_automation_resultreflect_add_prompt_stepreflect_add_segmentreflect_cancel_suite_executionreflect_connect_to_sessionreflect_create_segmentreflect_create_testreflect_delete_previous_stepreflect_execute_suitereflect_get_screenshotreflect_get_suite_execution_statusreflect_get_test_detailreflect_get_test_statusreflect_list_segmentsreflect_list_suite_executionsreflect_list_suitesreflect_list_testsreflect_run_testswagger_create_api_from_promptswagger_create_documentation_pageswagger_create_or_update_apiswagger_create_portalswagger_create_table_of_contentsswagger_delete_portal_productswagger_delete_table_of_contentsswagger_get_api_definitionswagger_get_documentswagger_get_portalswagger_list_organizationsswagger_list_portal_product_sectionsswagger_list_portalsswagger_list_table_of_contentsswagger_patch_apiswagger_publish_portal_productswagger_resolve_organization_portalswagger_scan_api_standardizationswagger_scan_api_standardization_from_registryswagger_search_apis_and_domainsswagger_standardize_apiswagger_update_documentswagger_update_portalzephyr_create_folderzephyr_create_test_casezephyr_create_test_case_issue_linkzephyr_create_test_case_stepszephyr_create_test_case_web_linkzephyr_create_test_cyclezephyr_create_test_cycle_issue_linkzephyr_create_test_cycle_web_linkzephyr_create_test_executionzephyr_create_test_execution_issue_linkzephyr_create_test_scriptzephyr_get_environmentszephyr_get_folderszephyr_get_issue_link_test_caseszephyr_get_prioritieszephyr_get_projectzephyr_get_projectszephyr_get_statuseszephyr_get_test_casezephyr_get_test_case_linkszephyr_get_test_case_stepszephyr_get_test_caseszephyr_get_test_cyclezephyr_get_test_cycle_linkszephyr_get_test_cycleszephyr_get_test_cycles_linked_to_a_jira_issuezephyr_get_test_executionzephyr_get_test_execution_linkszephyr_get_test_execution_stepszephyr_get_test_executionszephyr_get_test_executions_linked_to_a_jira_issuezephyr_get_test_planszephyr_get_test_scriptzephyr_update_test_casezephyr_update_test_cyclezephyr_update_test_executionzephyr_update_test_execution_steps
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
smartbear-mcp/0.42.0~0.43.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 10:32 PM UTC.- Distribution
npm- Previous release
@smartbear/mcp@0.42.0309 tools · published by the registry Oct 7, 2026, 8:25 AM UTCArtifact integritysha512-/i4c/TMfbaCrN/aJn5/ZEA7JYA5sxSI/NsY1ybYiQ0/GPJEA/h2z9DtYwhnTuynwAQdKLeqWgqPAArTwxaAFAg==Interface fingerprintsha256:2034b9edab2908a7c3b61ab94bfc89b9c411728618b42b06dc88797234899223Exact interface snapshot (JSON)- Current release
@smartbear/mcp@0.43.0316 tools · published by the registry Nov 3, 2026, 8:29 AM UTCArtifact integritysha512-GZ4v5Bvk495O7TCBu8oZuWGYYoWusGWnZnfKNSpxevl90n0AB7ffVhpLcgBBft4HuDdByM2ho3HdQ1GcGQNoNQ==Interface fingerprintsha256:cbd8ee679f1a17405b8e8ec499e8c7d3db99ed8cd63bb029ed44d7a9d18dbd0cExact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
111 findingscontract-testing_add_label_to_pacticipantREVIEWChangedShow details
output schema added
contract-testing_admin_add_role_to_userREVIEWChangedShow details
output schema added
contract-testing_admin_create_roleREVIEWChangedShow details
output schema added
contract-testing_admin_create_system_accountREVIEWChangedShow details
output schema added
contract-testing_admin_create_teamREVIEWChangedShow details
output schema added
contract-testing_admin_create_userREVIEWChangedShow details
output schema added
contract-testing_admin_delete_roleREVIEWChangedShow details
output schema added
contract-testing_admin_delete_teamREVIEWChangedShow details
output schema added
contract-testing_admin_delete_userREVIEWChangedShow details
output schema added
contract-testing_admin_get_roleREVIEWChangedShow details
output schema added
contract-testing_admin_get_system_account_tokensREVIEWChangedShow details
output schema added
contract-testing_admin_get_teamREVIEWChangedShow details
output schema added
contract-testing_admin_get_team_userREVIEWChangedShow details
output schema added
contract-testing_admin_get_userREVIEWChangedShow details
output schema added
contract-testing_admin_invite_usersREVIEWChangedShow details
output schema added
contract-testing_admin_list_permissionsREVIEWChangedShow details
output schema added
contract-testing_admin_list_rolesREVIEWChangedShow details
output schema added
contract-testing_admin_list_team_usersREVIEWChangedShow details
output schema added
contract-testing_admin_list_teamsREVIEWChangedShow details
output schema added
contract-testing_admin_list_usersREVIEWChangedShow details
output schema added
contract-testing_admin_patch_team_usersREVIEWChangedShow details
output schema added
contract-testing_admin_remove_role_from_userREVIEWChangedShow details
output schema added
contract-testing_admin_remove_user_from_teamREVIEWChangedShow details
output schema added
contract-testing_admin_reset_rolesREVIEWChangedShow details
output schema added
contract-testing_admin_set_team_usersREVIEWChangedShow details
output schema added
contract-testing_admin_set_user_rolesREVIEWChangedShow details
output schema added
contract-testing_admin_update_roleREVIEWChangedShow details
output schema added
contract-testing_admin_update_teamREVIEWChangedShow details
output schema added
contract-testing_admin_update_userREVIEWChangedShow details
output schema added
contract-testing_can_i_deployREVIEWChangedShow details
output schema added
contract-testing_check_pactflow_ai_entitlementsREVIEWChangedShow details
output schema added
contract-testing_create_environmentREVIEWChangedShow details
output schema added
contract-testing_create_pacticipantREVIEWChangedShow details
output schema added
contract-testing_create_secretREVIEWChangedShow details
output schema added
contract-testing_create_webhookREVIEWChangedShow details
output schema added
contract-testing_delete_all_integrationsREVIEWChangedShow details
output schema added
contract-testing_delete_branchREVIEWChangedShow details
output schema added
contract-testing_delete_environmentREVIEWChangedShow details
output schema added
contract-testing_delete_integrationREVIEWChangedShow details
output schema added
contract-testing_delete_pacticipantREVIEWChangedShow details
output schema added
contract-testing_delete_secretREVIEWChangedShow details
output schema added
contract-testing_delete_webhookREVIEWChangedShow details
output schema added
contract-testing_execute_webhookREVIEWChangedShow details
output schema added
contract-testing_generate_pact_testsREVIEWChangedShow details
output schema added
contract-testing_get_audit_logREVIEWChangedShow details
output schema added
contract-testing_get_bdct_consumer_by_consumer_versionREVIEWChangedShow details
output schema added
contract-testing_get_bdct_consumer_contract_verification_resultsREVIEWChangedShow details
output schema added
contract-testing_get_bdct_consumer_contractsREVIEWChangedShow details
output schema added
contract-testing_get_bdct_consumer_pact_test_results_by_consumerREVIEWChangedShow details
output schema added
contract-testing_get_bdct_cross-contract_verification_resultsREVIEWChangedShow details
output schema added
contract-testing_get_bdct_provider_by_consumer_versionREVIEWChangedShow details
output schema added
contract-testing_get_bdct_provider_check_results_by_consumerREVIEWChangedShow details
output schema added
contract-testing_get_bdct_provider_contractREVIEWChangedShow details
output schema added
contract-testing_get_bdct_provider_contract_verification_resultsREVIEWChangedShow details
output schema added
contract-testing_get_bdct_x-contract_test_results_by_consumerREVIEWChangedShow details
output schema added
contract-testing_get_branchREVIEWChangedShow details
output schema added
contract-testing_get_branch_versionsREVIEWChangedShow details
output schema added
contract-testing_get_current_userREVIEWChangedShow details
output schema added
contract-testing_get_currently_deployed_versionsREVIEWChangedShow details
output schema added
contract-testing_get_currently_supported_versionsREVIEWChangedShow details
output schema added
contract-testing_get_deployed_versions_for_versionREVIEWChangedShow details
output schema added
contract-testing_get_environmentREVIEWChangedShow details
output schema added
contract-testing_get_integrations_by_teamREVIEWChangedShow details
output schema added
contract-testing_get_latest_pacticipant_versionREVIEWChangedShow details
output schema added
contract-testing_get_metricsREVIEWChangedShow details
output schema added
contract-testing_get_pacticipantREVIEWChangedShow details
output schema added
contract-testing_get_pacticipant_labelREVIEWChangedShow details
output schema added
contract-testing_get_pacticipant_networkREVIEWChangedShow details
output schema added
contract-testing_get_pacticipant_versionREVIEWChangedShow details
output schema added
contract-testing_get_pacts_for_verificationREVIEWChangedShow details
output schema added
contract-testing_get_provider_statesREVIEWChangedShow details
output schema added
contract-testing_get_released_versions_for_versionREVIEWChangedShow details
output schema added
contract-testing_get_secretREVIEWChangedShow details
output schema added
contract-testing_get_system_preferencesREVIEWChangedShow details
output schema added
contract-testing_get_team_metricsREVIEWChangedShow details
output schema added
contract-testing_get_user_preferencesREVIEWChangedShow details
output schema added
contract-testing_get_webhookREVIEWChangedShow details
output schema added
contract-testing_list_api_tokensREVIEWChangedShow details
output schema added
contract-testing_list_branchesREVIEWChangedShow details
output schema added
contract-testing_list_environmentsREVIEWChangedShow details
output schema added
contract-testing_list_integrationsREVIEWChangedShow details
output schema added
contract-testing_list_labelsREVIEWChangedShow details
output schema added
contract-testing_list_pacticipant_versionsREVIEWChangedShow details
output schema added
contract-testing_list_pacticipantsREVIEWChangedShow details
output schema added
contract-testing_list_pacticipants_by_labelREVIEWChangedShow details
output schema added
contract-testing_list_secretsREVIEWChangedShow details
output schema added
contract-testing_list_webhooksREVIEWChangedShow details
output schema added
contract-testing_matrixREVIEWChangedShow details
output schema added
contract-testing_patch_pacticipantREVIEWChangedShow details
output schema added
contract-testing_publish_consumer_contractsREVIEWChangedShow details
output schema added
contract-testing_publish_provider_contractREVIEWChangedShow details
output schema added
contract-testing_record_deploymentREVIEWChangedShow details
output schema added
contract-testing_record_releaseREVIEWChangedShow details
output schema added
contract-testing_regenerate_api_tokenREVIEWChangedShow details
output schema added
contract-testing_remove_label_from_pacticipantREVIEWChangedShow details
output schema added
contract-testing_review_pact_testsREVIEWChangedShow details
output schema added
contract-testing_test_execute_webhooksREVIEWChangedShow details
output schema added
contract-testing_update_environmentREVIEWChangedShow details
output schema added
contract-testing_update_pacticipantREVIEWChangedShow details
output schema added
contract-testing_update_pacticipant_versionREVIEWChangedShow details
output schema added
contract-testing_update_secretREVIEWChangedShow details
output schema added
contract-testing_update_webhookREVIEWChangedShow details
output schema added
qmetry_bulk_update_test_case_execution_statusREVIEWChangedShow details
input property added: udfValuesByRuninput property added: viewId
qmetry_execute_quality_gate_reportREVIEWChangedShow details
input property added: extKeys
qmetry_update_issueREVIEWChangedShow details
input property affectedCycles changed: +items={"type":"number"}, type "number" → "array"
qmetry_update_test_caseREVIEWChangedShow details
input property added: testcaseOwnerinput property removed: owner
swagger_create_portal_productREVIEWChangedShow details
input property added: visibilityinput property removed: hiddenoutput property added: visibilityoutput property removed: hidden
swagger_get_portal_productREVIEWChangedShow details
output property added: visibilityoutput property removed: hidden
swagger_list_portal_productsREVIEWChangedShow details
output property items changed: items {"additionalPropert… → {"additionalPropert…
swagger_update_portal_productREVIEWChangedShow details
input property added: visibilityinput property removed: hiddenoutput property added: visibilityoutput property removed: hidden
swagger_validate_apiREVIEWChangedShow details
output property findings changed: items {"additionalPropert… → {"additionalPropert…output property summary changed: properties {"durationMs":{"typ… → {"durationMs":{"typ…
Informational
17 findingsbearq_get_workflow_runINFOAddedbearq_list_workflowsINFOAddedbearq_run_workflowINFOAddedbearq_stop_workflow_runINFOAddedcontract-testing_list_deployed_or_released_versionsINFOAddedcontract-testing_list_environment_versionsINFOAddedqmetry_fetch_api_call_quotaINFOAddedbearq_stop_taskINFOChangedqmetry_bulk_update_test_case_execution_statusINFOChangedqmetry_execute_quality_gate_reportINFOChangedqmetry_fetch_executions_by_test_suiteINFOChangedqmetry_fetch_test_case_runs_by_test_suite_runINFOChangedqmetry_update_issueINFOChangedqmetry_update_test_caseINFOChangedswagger_create_portal_productINFOChangedswagger_update_portal_productINFOChangedswagger_validate_apiINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.