Skip to main content
Glama

Recent role changes

recent_changes
Read-onlyIdempotent

Recently added, removed, renamed or re-permissioned Microsoft 365 and Azure roles, newest first. The same entries as RBAC Map's What's New feed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 20, max 50).
sinceNoOnly changes on or after this date (YYYY-MM-DD).
serviceNoLimit to one service, e.g. "entra" or "azure".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds ordering (newest first) and identifies the content as mirroring RBAC Map's What's New feed, which helps set expectations about completeness. It does not describe truncation or return shape, but with no output schema and full annotation coverage this is a modest gap.

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

Conciseness4/5

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

Two tight sentences with the scope and ordering front-loaded and zero filler. The second sentence adds orientation rather than restating the first.

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?

For a read-only, zero-required-parameter list tool with a fully documented schema and no output schema, the definition covers what the entries are, their ordering, and their provenance. Only the return shape and truncation behavior remain unstated, which is a minor omission.

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 description coverage is 100%, with limit, since and service all documented inline including the default and maximum for limit and the enum for service. The description adds nothing about parameter semantics, which is acceptable at the baseline for fully documented schemas.

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 resource (Microsoft 365 and Azure roles) and enumerates the change types captured (added, removed, renamed, re-permissioned), plus the sort order. It is clearly distinct from siblings like get_role or compare_roles by being a chronological change feed, though it never names an alternative 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: an agent can infer this is for browsing recent RBAC changes rather than inspecting a single role. There is no explicit when-to-use, when-not-to-use, or routing to siblings such as compare_roles for diffs or search_roles for lookup.

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