Skip to main content
Glama

Compare roles

compare_roles
Read-onlyIdempotent

Compare 2 or 3 roles: the permissions they share and the permissions only one of them has, with each role's privilege tier.

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": {
      "ids": "<ids>"
    },
    "name": "compare_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRole ids from search_roles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing what the comparison returns — shared permissions, permissions held by only one role, and each role's privilege tier — which an agent could not infer from the annotations or the one-parameter schema.

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?

A single front-loaded sentence that packs the cardinality, the output composition, and the privilege-tier detail with no filler or redundancy.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so adequately in one clause. Minor omissions remain — result ordering, behavior on duplicate or invalid ids, and output format — but nothing that would prevent correct invocation.

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% and the single 'ids' parameter is documented with its source (search_roles), minItems/maxItems, and item type. The description only echoes the 2-3 range already encoded in the schema, adding no further format or ordering guidance, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ('Compare ... roles') and specifies the cardinality (2 or 3) plus the substance of the result (shared permissions, permissions unique to one role, privilege tier). It clearly differs from a single-role lookup like get_role, though it never names a sibling explicitly.

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?

Usage is only implied: the cardinality constraint and the schema note that ids come from search_roles suggest the intended workflow, but the description itself gives no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_role for single-role inspection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources