iSuite Operations MCP Server

verify_user_permission

Check whether a user has a given permission, returning true or false with context. Supports optional resource scoping for granular access verification.

Instructions

Check whether a specific user has a given permission. Returns true/false with context.

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": {
      "userId": "<userId>",
      "permission": "<permission>"
    },
    "name": "verify_user_permission"
  }
}

Input Schema

Name	Required	Description
`userId`	Yes	The user's unique ID or username.
`permission`	Yes	The permission identifier to check (e.g. 'jobs.cancel', 'batch.rerun', 'audit.export').
`resource`	No	Optional specific resource ID to check scoped permission against.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (true/false with context) and implies no side effects. However, it doesn't mention auth requirements or rate limits, which are acceptable for a simple read operation.

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 a single concise sentence that clearly conveys the tool's purpose and return value. No unnecessary words or fluff.

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

Completeness4/5

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

Given no output schema, the description adequately explains the return type but the phrase 'with context' is vague. For a simple boolean check tool, this is sufficient, but could be more precise for clarity.

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?

The input schema has 100% coverage, so baselining at 3. The description does not add extra meaning beyond the schema's parameter descriptions. It succinctly summarizes the function but provides no additional parameter semantics.

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 action: checking if a user has a specific permission. It specifies the resource (user permission) and the return type (true/false with context), distinguishing it from sibling tools that modify permissions like assign_role or revoke_role.

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 implies usage for permission verification but lacks explicit guidance on when to use this tool versus alternatives. No mention of prerequisites or when not to use, which would be helpful given the many sibling tools.

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