Skip to main content
Glama

get_team

Retrieve detailed information about a specific team using its unique identifier. This tool helps access team data from the Devici threat modeling platform for management purposes.

Instructions

Get a specific team by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_team': decorated with @mcp.tool(), fetches team data via API client and returns as string.
    @mcp.tool()
    async def get_team(team_id: str) -> str:
        """Get a specific team by ID"""
        async with create_client_from_env() as client:
            result = await client.get_team(team_id)
            return str(result)
  • API client method implementing the HTTP GET request to retrieve a specific team by ID from the Devici API.
    async def get_team(self, team_id: str) -> Dict[str, Any]:
        """Get specific team by ID."""
        return await self._make_request("GET", f"/teams/{team_id}")
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this is a read-only operation (implied but not stated), authentication needs, error handling, rate limits, or what happens if the team ID doesn't exist. The description is minimal and lacks necessary context for safe invocation.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information immediately.

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?

Given the tool's simplicity (1 parameter, has output schema) but lack of annotations, the description is minimally adequate. The output schema existence means return values don't need explanation, but the description should still cover more behavioral aspects for a complete understanding. It meets basic requirements but has clear gaps.

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?

The description mentions 'by ID' which adds meaning to the 'team_id' parameter beyond what the schema provides (0% coverage, just title 'Team Id'). However, it doesn't explain the ID format, source, or constraints. With 1 parameter and low schema coverage, this provides basic but incomplete semantic context.

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?

The description clearly states the verb ('Get') and resource ('a specific team by ID'), making the purpose unambiguous. It distinguishes from the sibling 'get_teams' by specifying retrieval of a single team rather than multiple teams. However, it doesn't fully differentiate from other get_* tools like 'get_user' or 'get_collection' beyond the resource type.

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 description implies usage when you need a specific team identified by ID, but doesn't explicitly state when to use this versus alternatives like 'get_teams' for listing teams or other get_* tools for different resources. No guidance on prerequisites or exclusions is provided.

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

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/geoffwhittington/devici-mcp'

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