Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scf_list_teams

Read-only

List an organization's teams, optionally filtered by business function or membership, and include archived teams to preserve full history.

Instructions

List the organization's teams (read — viewer role). Archived teams are hidden unless include_inactive is set; they are kept, never deleted, so history still resolves.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mineNoOnly teams the caller is a member of (default false); each team then also carries membership_role. 'The caller' is the API key's identity; on a self-hosted instance that is a service account on no team, so this returns nothing — use team_id instead.
org_idYesOrganization UUID — obtain from scf_list_organizations
function_idNoFilter by business function — obtain from scf_list_functions
include_inactiveNoInclude archived teams (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.6.0
    • addedInput schema / properties / mine
      Added value: +{
+  "default": false,
+  "description": "Only teams the caller is a member of (default false); each team then also carries membership_role. 'The caller' is the API key's identity; on a self-hosted instance that is a service account on no team, so this returns nothing — use team_id instead.",
+  "type": "boolean"
+}
  2. Addedv3.4.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, lowering the burden on the description. The description adds valuable behavioral context: archived teams are hidden by default, are 'kept, never deleted,' and history still resolves. This goes beyond the annotation and helps an agent understand the archival semantics.

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?

The description is a single front-loaded sentence with no wasted words. It states the core action, the permission level, and the key archive behavior efficiently. Every clause adds information relevant to calling the tool.

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 list operation with a readOnlyHint and fully documented parameters, the description covers the main behavioral nuance (archived teams) and permission context. No output schema exists, but the tool's purpose and filtering behavior are sufficiently clear for an agent to invoke it correctly. Minor details like pagination or return shape are not disclosed, but these are not critical for this simple list operation.

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 the schema already fully documents all four parameters. The description adds a small amount of semantics by explaining the include_inactive behavior, but mostly relies on the schema. Baseline 3 is appropriate because the schema carries the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List the organization's teams,' which clearly identifies the operation. It also adds distinguishing context ('Archived teams are hidden unless include_inactive is set') that sets it apart from other list tools. The parenthetical 'read — viewer role' reinforces its read-only nature.

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?

The description gives clear context: this is a read operation for viewer role, and archived teams are only included when include_inactive is set. It does not explicitly name sibling alternatives like scf_get_team for single-team retrieval, but the scope and conditions are clear enough to guide selection. No misleading or exclusions are present.

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