Skip to main content
Glama

List the teams I can read

standcast_list_teams
Read-onlyIdempotent

Lists teams you manage, or all teams for an organization admin, so you can select which teams to read with the other manager tools.

Instructions

Lists the teams the person manages, or every team for an organization admin. Only these teams can be read with the other manager tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "standcast_list_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization login. Optional when the person belongs to a single organization.

Output Schema

NameRequiredDescriptionDefault
dataYes
untrustedYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the non-obvious behavioral fact that results are role-scoped and act as an authorization boundary for other tools, which the annotations cannot convey. Return shape and pagination for large admin listings are left unstated, though an output schema exists.

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 sentences, no filler. Scope is front-loaded and the dependency on other manager tools follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with full annotation coverage and an output schema, the description covers who sees what, why the result matters, and how it gates other tools. Nothing essential to correct invocation is missing.

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?

There is a single parameter with 100% schema description coverage, including the condition that 'org' is optional for single-organization users. The description adds role context ('organization admin') but nothing about the org argument itself, so it neither compensates for nor extends 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?

States a specific verb ('Lists') and resource ('teams') and clarifies that the result set depends on role: managed teams for a manager, all teams for an org admin. It is clearly distinguishable from the daily/blocker/digest siblings, though it never names a sibling directly.

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 sentence 'Only these teams can be read with the other manager tools' effectively tells the agent this is a discovery/prerequisite call before other manager operations. It stops short of an explicit 'call this first' instruction or any when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.