Skip to main content
Glama

Find admin tasks

list_tasks
Read-onlyIdempotent

Search the admin tasks RBAC Map maps to roles (e.g. "reset MFA", "create retention policy"), with the least-privileged roles that can do each one.

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": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 20, max 50).
queryNoKeywords describing the task.
serviceNoLimit to one service, e.g. "entra" or "azure".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by stating what comes back — the least-privileged roles capable of each task — which is the key behavioral detail an agent needs. It says nothing about result volume, ordering, or empty-result behavior, though the schema covers the limit.

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

Conciseness3/5

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

It is a single short sentence with no filler, and the resource is front-loaded. However, the mangled clause "the admin tasks RBAC Map maps to roles" costs a re-read, so brevity is undercut by poor phrasing rather than by length.

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 lookup tool with rich annotations, a fully documented three-parameter schema, and no output schema, the description covers what it searches and what it returns (tasks paired with least-privileged roles). Only the sibling differentiation and any result-shape caveats are missing, which is a minor gap given the structured fields.

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%, so the schema already documents limit, query, and service, including the enum values and default. The description only implicitly reinforces the query concept via the example task phrases ("reset MFA", "create retention policy"), adding marginal meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose3/5

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

The description conveys the core idea — search admin tasks and see which least-privileged roles can perform each — but the opening clause is grammatically garbled ("Search the admin tasks RBAC Map maps to roles"), forcing the agent to reconstruct the meaning. The verb+resource is present, yet it never contrasts itself with role-centric siblings such as find_roles_with_permission or search_roles.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, despite siblings that overlap conceptually (find_roles_with_permission, search_roles, compare_roles). At best, usage is implied by the example phrases "reset MFA" and "create retention policy", which suggest a task-first, least-privilege lookup scenario.

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