Semata

Restore role criteria

restore_role_criteria

Destructive

Undo the most recent update_role_criteria or restore_role_criteria change on a role. Only use this when the user asks to undo. Pass previousCriteria and previousDescription from that result unchanged; never reconstruct them. Eligible existing candidates are brought in line with the restored criteria. Requires OAuth or a scoped token, and a workspace role that can edit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "roleId": "<roleId>",
      "previousCriteria": "<previousCriteria>",
      "previousDescription": "<previousDescription>"
    },
    "name": "restore_role_criteria"
  }
}

Input Schema

Name	Required	Description
`roleId`	Yes	The role id from the criteria update result.
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.
`previousCriteria`	Yes	The exact previousCriteria object from the criteria update result.
`previousDescription`	Yes	The exact previousDescription from the criteria update result.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true but say nothing about scope; the description adds that the undo affects 'eligible existing candidates [brought] in line with the restored criteria,' which is the key side effect. It also discloses auth requirements ('OAuth or a scoped token, and a workspace role that can edit'), which annotations never cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, each carrying a distinct load: what it does, when to use, how to source parameters, side effect, and auth. The undo semantics are front-loaded before the mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a nested previousCriteria object with no output schema, the description covers purpose, prerequisite inputs, side effects, and authorization. Nothing an agent needs to invoke this destructive undo safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter is already documented, so baseline is 3. The description goes beyond by instructing that previousCriteria and previousDescription must be passed 'unchanged; never reconstruct them,' a correctness constraint the schema cannot express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Undo the most recent update_role_criteria or restore_role_criteria change on a role'), which immediately distinguishes it from the sibling update_role_criteria. An agent can tell what it does and what it reverses without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gates usage: 'Only use this when the user asks to undo,' which is a clear when-to-use condition and implicitly excludes proactive use. It also names the originating tool whose result supplies the inputs, giving the agent the full workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Semata tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?