Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_expiring_grants

Read-only

Lists grants expiring within a specified number of days so admins can renew or revoke them before workflows break.

Instructions

Return grants set to expires_at within the next within_days. Lets admins renew or revoke before they lapse and break workflows. Business+ 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": {
      "org_id": "<org_id>"
    },
    "name": "list_expiring_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org whose grants are reviewed.
within_daysNoList grants that expire between now and this many days from now. Grants with no expiry are never listed. Defaults to ``30``. Default: 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value the annotations cannot: a plan-tier entitlement requirement (Business+) and the downstream admin action the list supports. It omits result-size/pagination behavior, which keeps it at 4 rather than 5.

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 core action and followed by the rationale plus tier constraint; nothing is padded. The backtick/markdown emphasis on field names is slightly noisy but does not impede reading.

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 two-parameter read-only listing with no output schema, the description covers what is returned, the time window, the admin use case, and the tier gate. The only gap is that the shape of a returned grant record is not hinted at, which is acceptable given the tool's simplicity.

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 org_id and within_days (including the default of 30 and the rule that never-expiring grants are excluded) are already fully documented. The description only restates the within_days window and adds no syntax or edge-case meaning beyond the schema, 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?

States a specific verb and resource: return grants whose expires_at falls within the next within_days. An agent can immediately tell this is a time-windowed listing of grants. It does not name a sibling such as list_stale_grants or list_scopes to sharpen the boundary, which keeps it below a 5.

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?

Gives a clear operational context ('lets admins renew or revoke before they lapse and break workflows') and a hard prerequisite ('Business+ tier'), which is genuine when-to-use guidance. It stops short of explicit exclusions or naming an alternative tool for adjacent needs, so it is not a 5.

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