Skip to main content
Glama

create_approval_rule

Automatically generate approval requests when records meet conditions, by defining the rule name, table, and approver.

Instructions

Create an approval rule that automatically generates approval requests when a record matches given conditions (requires WRITE_ENABLED=true). Uses the sysapproval_rule table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRule name
tableYesTable this rule applies to (e.g. "sc_request", "change_request")
approver_typeYes"user" | "group" — whether the approver is a user or a group
approverYessys_id of the approving user or group
conditionNoEncoded query that determines when the rule fires (leave blank for always)
activeNoActivate the rule immediately (default: true)
orderNoExecution order relative to other rules (default: 100)
Behavior3/5

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

The description discloses that the tool is a mutation and requires a specific permission, which adds value beyond annotations (which already indicate no readOnlyHint). However, it does not detail side effects, reversibility, or what happens upon rule creation, leaving some behavioral gaps.

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?

The description is extremely concise with two sentences, front-loading the purpose and requirement. Every sentence provides essential information without redundancy.

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

Completeness3/5

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

Given the high schema coverage and no output schema, the description is minimally adequate but lacks details about the rule's lifecycle, integration with approval flows, or error conditions. It is sufficient for a basic understanding but not comprehensive.

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

Parameters3/5

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

Schema coverage is 100%, with all parameters described in the schema. The description adds no additional parameter-level meaning beyond what is already in the input schema, so a baseline of 3 is appropriate.

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?

The description clearly states the verb 'create' and the resource 'approval rule', and explains its function: automatically generating approval requests when a record matches conditions. It also mentions a prerequisite and the underlying table, distinguishing it from other 'create_*' siblings.

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

Usage Guidelines3/5

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

The description mentions a precondition (WRITE_ENABLED=true) but does not provide explicit guidance on when to use this tool versus alternatives like approve_request or list_approvals. Usage is implied but not clearly bounded.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tedorigawa001/ServiceNow-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server