Skip to main content
Glama
Rootly-AI-Labs

Rootly MCP server

Official

listTeams

Retrieve and filter teams using query parameters such as name, slug, external IDs, and creation dates, with pagination support for efficient team management.

Instructions

List teams

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_slug: No description.

  • filter_name: No description.

  • filter_backstage_id: No description.

  • filter_cortex_id: No description.

  • filter_opslevel_id: No description.

  • filter_external_id: No description.

  • filter_color: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_backstage_idNo
filter_colorNo
filter_cortex_idNo
filter_created_at_gtNo
filter_created_at_gteNo
filter_created_at_ltNo
filter_created_at_lteNo
filter_external_idNo
filter_nameNo
filter_opslevel_idNo
filter_searchNo
filter_slugNo
includeNo
page_numberNo
page_sizeNo
sortNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the OpenAPI specification as MCP tools via FastMCP.from_openapi. The 'listTeams' tool is generated from the GET /teams (or /v1/teams) endpoint defined in the Rootly API OpenAPI spec.
    # By default, all routes become tools which is what we want
    mcp = FastMCP.from_openapi(
        openapi_spec=filtered_spec,
        client=http_client.client,
        name=name,
        timeout=30.0,
        tags={"rootly", "incident-management"},
    )
  • DEFAULT_ALLOWED_PATHS list includes '/teams' which is filtered into the OpenAPI spec used for tool generation, enabling the listTeams tool.
    DEFAULT_ALLOWED_PATHS = [
        "/incidents/{incident_id}/alerts",
        "/alerts",
        "/alerts/{alert_id}",
        "/severities",
        "/severities/{severity_id}",
        "/teams",
        "/teams/{team_id}",
        "/services",
        "/services/{service_id}",
        "/functionalities",
        "/functionalities/{functionality_id}",
        # Incident types
        "/incident_types",
        "/incident_types/{incident_type_id}",
        # Action items (all, by id, by incident)
        "/incident_action_items",
        "/incident_action_items/{incident_action_item_id}",
        "/incidents/{incident_id}/action_items",
        # Workflows
        "/workflows",
        "/workflows/{workflow_id}",
        # Workflow runs
        "/workflow_runs",
        "/workflow_runs/{workflow_run_id}",
        # Environments
        "/environments",
        "/environments/{environment_id}",
        # Users
        "/users",
        "/users/{user_id}",
        "/users/me",
        # Status pages
        "/status_pages",
        "/status_pages/{status_page_id}",
        # On-call schedules and shifts
        "/schedules",
        "/schedules/{schedule_id}",
        "/schedules/{schedule_id}/shifts",
        "/shifts",
        "/schedule_rotations/{schedule_rotation_id}",
        "/schedule_rotations/{schedule_rotation_id}/schedule_rotation_users",
        "/schedule_rotations/{schedule_rotation_id}/schedule_rotation_active_days",
        # On-call overrides
        "/schedules/{schedule_id}/override_shifts",
        "/override_shifts/{override_shift_id}",
        # On-call shadows and roles
        "/schedules/{schedule_id}/on_call_shadows",
        "/on_call_shadows/{on_call_shadow_id}",
        "/on_call_roles",
        "/on_call_roles/{on_call_role_id}",
    ]
  • AuthenticatedHTTPXClient.request() is the generic handler executed by generated OpenAPI tools like listTeams to make authenticated HTTP requests to the Rootly API (GET /v1/teams).
    async def request(self, method: str, url: str, **kwargs):
        """Override request to transform parameters."""
        # Transform query parameters
        if 'params' in kwargs:
            kwargs['params'] = self._transform_params(kwargs['params'])
    
        # Call the underlying client's request method and let it handle everything
        return await self.client.request(method, url, **kwargs)
  • Prepends /v1 prefix to paths like /teams before filtering the OpenAPI spec, ensuring the listTeams endpoint is correctly included.
    allowed_paths_v1 = [
        f"/v1{path}" if not path.startswith("/v1") else path
        for path in allowed_paths
    ]
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions a 200 success response with example JSON, but provides no meaningful behavioral information about pagination behavior, rate limits, authentication requirements, error conditions, or what 'success' actually means. The example JSON with 'key': 'value' is completely uninformative about actual response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is structured with sections, it's not appropriately sized for its purpose. The parameter listing with 'No description' repeated 16 times adds bulk without value. The example response with generic 'key': 'value' is wasted space. The description is simultaneously verbose (repetitive parameter formatting) and under-specified (lacking meaningful content).

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

Completeness1/5

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

For a tool with 16 parameters, 0% schema description coverage, no annotations, and complex filtering capabilities, this description is completely inadequate. While there is an output schema (implied by 'Has output schema: true'), the description provides no meaningful context about what teams are, how filtering works, pagination behavior, or response format. The example JSON is useless for understanding actual return values.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for 16 undocumented parameters. While it lists all parameter names, every single one is marked 'No description.' The description adds no semantic meaning beyond what's already in the schema property names. Parameters like 'filter_backstage_id', 'filter_cortex_id', 'filter_opslevel_id' remain completely unexplained despite being critical filtering options.

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

Purpose2/5

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

The description states 'List teams' which is a tautology of the tool name 'listTeams'. It provides no additional context about what 'teams' are in this system, what information is returned, or how this differs from other list tools like 'listUsers' or 'listServices'. While it does specify the verb+resource, it doesn't distinguish from siblings or provide meaningful purpose clarification beyond the obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. There are multiple other list/search tools in the sibling set (listAlerts, listIncidents, listServices, etc.), but no indication of when teams listing is appropriate versus other entity types. No prerequisites, no exclusions, no comparison to similar tools.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rootly-AI-Labs/Rootly-MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server