Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_my_teams

Read-only

List the teams a tenant belongs to within a given org. Use it to check a caller's team memberships before assigning work or permissions.

Instructions

List teams within org_id that tenant_id belongs to.

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

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org whose teams are searched.
tenant_idYesThe account whose team memberships are listed. On Kiln's hosted server it is always the signed-in caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / org_id / description
      Added value: +"The org whose teams are searched."
    • addedInput schema / properties / tenant_id / description
      Added value: +"The account whose team memberships are listed.  On Kiln's hosted server it is always the signed-in caller."
  2. Addedv1.5.0

TDQS

B3.4/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 safety is covered. The description contributes the key behavioral fact that results are filtered to the tenant's memberships rather than returning all teams, but says nothing about ordering, pagination, or empty results.

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?

A single front-loaded sentence with no filler, so nothing needs trimming. The relational phrasing 'within org_id that tenant_id belongs to' is slightly awkward to parse but not wasteful.

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 tool with full schema coverage and clear annotations, this is close to sufficient. The remaining gap is disambiguation from the sibling list_teams, which the description never addresses.

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 itself documents both org_id and tenant_id, including the note that tenant_id is the signed-in caller on hosted servers. The description only restates the same two identifiers, adding no syntax or edge-case meaning.

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 (list) plus resource (teams) and narrows scope to the teams within org_id that the given tenant belongs to, which is meaningfully more precise than the name alone. It does not, however, explicitly contrast itself with the sibling list_teams, which an agent could easily confuse it with.

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?

Usage is only implied: the phrase 'that tenant_id belongs to' suggests 'use this when you want the caller's own memberships', but the description never says when to pick this over list_teams or list_team_members. No prerequisites or exclusions are given.

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