Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_org_members

Read-only

Lists every member of a Kiln Business organisation with their assigned role. Use it to check who belongs to an org and what each member can do.

Instructions

List every member of org_id with their role.

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

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org whose members are listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / org_id / description
      Added value: +"The org whose members are listed."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior3/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 the plan-entitlement constraint, which is real value beyond the annotations, but says nothing about permission requirements, pagination, or result ordering for large orgs.

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, the action is front-loaded, and the entitlement caveat follows immediately with no filler. Every sentence carries information an agent would otherwise not have.

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 one-parameter read-only listing tool with full annotation coverage and no output schema, the description covers what it does, what it returns (members plus roles), and the plan precondition. Only the entitlement-failure behavior and result size expectations are left unstated, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema description coverage, the schema already fully documents org_id, so the baseline applies. The description restates which org is being enumerated and confirms the returned records carry a role, adding a small amount of meaning about what is keyed off the parameter.

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 uses a clear verb and resource ('List every member of org_id with their role') and states the scope is a single organisation. It does not name the nearby alternatives (list_team_members, list_my_orgs, remove_org_member), so an agent must infer the org-vs-team distinction from the name alone.

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?

The prerequisite 'Needs the organisation to be on Kiln Business' is genuinely useful gating guidance that would otherwise surface only as a runtime error. However, there is no explicit when-to-use or when-not-to-use guidance against the sibling member-listing tools, so the selection logic is only implied.

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