Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_my_orgs

Read-only

Retrieve all organizations a tenant_id belongs to as owner or member, so you can identify the account's memberships and access scope.

Instructions

Return every org tenant_id belongs to (owner or member).

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "list_my_orgs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesThe account whose orgs are listed. On Kiln's hosted server it is always the signed-in caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / tenant_id / description
      Added value: +"The account whose orgs are listed.  On Kiln's hosted server it is always the signed-in caller."
  2. Addedv1.5.0

TDQS

A3.5/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 useful detail that results include both owned and member orgs, but says nothing about result ordering, pagination, or what happens with an unknown tenant_id.

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?

A single front-loaded sentence with no filler; the scope qualifier '(owner or member)' is the only clause and it carries real information about result contents.

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 simple single-parameter read tool with annotations and no output schema, the description is adequate but thin: it never describes the shape of the returned orgs (ids, names, role) or whether the list can be empty, which is the main remaining question an agent would have.

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% and the schema's tenant_id description already explains that on the hosted server it is always the signed-in caller. The description only restates that tenant_id selects the account, adding no syntax or format meaning 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?

Names a specific verb ('Return') and resource ('every org'), and scopes it to orgs the given tenant_id belongs to as owner or member. This naturally distinguishes it from siblings like list_my_teams or list_org_members, though it never names those alternatives explicitly.

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 parenthetical '(owner or member)' implies the use case of discovering a user's org affiliations, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as list_my_teams or list_org_members for the related but different question.

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