Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_scopes

Read-only

List organization grants in Kiln Business, optionally filtering by tenant or team to review access scopes.

Instructions

List grants for an org, optionally filtered by tenant OR team.

Needs the organisation to be on Kiln Business.

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_scopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org whose grants are listed.
team_idNoOnly list grants made to this team. Omit it, and ``tenant_id``, to list every grant in the org.
tenant_idNoOnly list grants made to this account. Omit it, and ``team_id``, to list every grant in the org.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / org_id / description
      Added value: +"The org whose grants are listed."
    • addedInput schema / properties / team_id / description
      Added value: +"Only list grants made to this team.  Omit it, and ``tenant_id``, to list every grant in the org."
    • addedInput schema / properties / tenant_id / description
      Added value: +"Only list grants made to this account.  Omit it, and ``team_id``, to list every grant in the org."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds the Kiln Business prerequisite, but does not describe pagination, result limits, or whether inherited grants are included.

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?

Two short sentences, front-loaded with purpose and prerequisite. No redundant wording or unnecessary detail.

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 low-complexity read-only list tool with full schema coverage and annotations, the description covers purpose, filters, and tier prerequisite. It could be more complete by naming related grant-list tools or mentioning pagination behavior, but those are secondary here.

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 each parameter is already fully documented in the schema. The description adds only the 'tenant OR team' filtering concept, which is mostly covered by the schema and slightly ambiguous.

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 ('List grants for an org') and notes optional tenant/team filters. It does not distinguish this tool from sibling grant-listing tools such as list_expiring_grants or list_stale_grants.

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?

Provides a clear basic context (list grants, optionally filter by tenant or team) and a prerequisite (Kiln Business). It does not give explicit when-to-use guidance versus alternatives, and the 'tenant OR team' wording is ambiguous when both filters are supplied.

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