Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_stale_grants

Read-only

Find grants in an organization older than a specified number of days to support quarterly access reviews and confirm whether long-untouched permissions are still needed.

Instructions

Return every grant in org_id whose granted_at is older than older_than_days. The quarterly access-review starting point: "these grants have been untouched for 3 months — still needed?" Business+ tier (team access review).

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": {
      "org_id": "<org_id>"
    },
    "name": "list_stale_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org whose grants are reviewed.
older_than_daysNoList grants made more than this many days ago. Defaults to ``90``. Default: 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this as a non-destructive, closed-world read, so the bar is lower; the description usefully adds the "Business+ tier" entitlement requirement, which annotations do not convey. However, the "untouched for 3 months" framing is imprecise — the filter is on granted_at, not on last-use — and no pagination or result-size behavior is disclosed.

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 sentences, front-loaded with the operation and filter, followed by the use case. Slightly cluttered by escaped quotation marks and a parenthetical tier note, but nothing is padded or redundant.

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?

For a two-parameter read-only list tool with no output schema, the definition covers what it returns conceptually and why. It leaves unanswered what a grant record contains, whether results are paginated or ordered, and how a caller should interpret the returned set.

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 both org_id and older_than_days documented including the 90-day default, so the schema carries the parameter burden. The description adds only the granted_at comparison basis and the practical three-month framing, which is modest value beyond the schema.

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?

States a specific verb and resource ("Return every grant") plus the exact filter predicate (granted_at older than older_than_days), which separates it from the expiry-oriented sibling list_expiring_grants. It stops short of naming that sibling explicitly, so the distinction must be inferred from the predicate rather than stated.

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

Usage Guidelines4/5

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

The description frames a concrete occasion for use — "the quarterly access-review starting point" — with a quoted reviewer question that makes intent unambiguous. It gives a positive when-to-use case but no explicit exclusions or named alternatives for adjacent tools.

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

Deploy Server

Other Tools