Skip to main content
Glama
adepanges

TeamRetro MCP Server

by adepanges
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

detail_team

Retrieve detailed information about a specific team by its unique ID using the TeamRetro MCP Server for precise team retrospective management.

Instructions

Get a single team by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesstring

Implementation Reference

  • src/features/teams/tools.ts:30-35 (handler)
    Primary definition and handler for the 'detail_team' tool. Includes input schema (requiring team ID), description, and async handler that invokes teamsService.getTeam to fetch team details.
    detail_team: {
  schema: teamSchema.pick({ id: true }),
  description: "Retrieve detailed information about a single team by its unique ID",
  handler: async (args: { id: string }) =>
    createToolResponse(teamsService.getTeam(args.id)),
},
  • src/features/teams/service.ts:34-36 (helper)
    Supporting service method that executes the core logic: HTTP GET request to the /v1/teams/{id} API endpoint to retrieve detailed team information.
    async getTeam(teamId: string): Promise<SingleApiResponse<Team>> {
  return this.get<SingleApiResponse<Team>>(`/v1/teams/${teamId}`);
}
  • src/tools.ts:13-22 (registration)
    Global registration of feature tools, including teamTools containing 'detail_team', by spreading into the main tools object for schema generation and handler mapping.
    const tools = {
  ...userTools,
  ...teamTools,
  ...teamMembersTools,
  ...actionTools,
  ...retrospectiveTools,
  ...agreementTools,
  ...healthModelTools,
  ...healthCheckTools,
};
  • src/features/teams/tools.ts:31-31 (schema)
    Input schema for detail_team tool: Zod schema picking only the 'id' field from teamSchema for validation.
    schema: teamSchema.pick({ id: true }),
  • src/tools.ts:15-15 (registration)
    Specific inclusion of teamTools (with detail_team) in the main tools registry.
    ...teamTools,

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read operation, but doesn't mention whether it requires authentication, has rate limits, returns error conditions, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core purpose without any fluff. It's front-loaded with the essential information ('Get a single team by ID'), making it immediately clear. Every word earns its place, with no wasted verbiage.

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 simple single-parameter input schema with full coverage and no output schema, the description is minimally adequate. It covers the basic purpose but lacks behavioral details like authentication needs, error handling, or output format. For a read operation with no annotations, it should ideally provide more context about what 'Get' entails beyond just the action.

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%, with the single parameter 'teamId' fully documented in the schema including its type, pattern, and requirement. The description adds no additional parameter information beyond what's in the schema, such as explaining what a team ID represents or where to find it. Baseline 3 is appropriate when the schema does all the work.

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 action ('Get') and resource ('a single team by ID'), making the purpose immediately understandable. It distinguishes this from list_teams by specifying retrieval of a single team rather than multiple teams. However, it doesn't explicitly contrast with other sibling tools like get_user or list_team_members, keeping it from a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use detail_team versus list_teams, get_user, or list_team_members, nor does it specify prerequisites like needing a team ID. Without any usage context, the agent must infer when this tool is appropriate.

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/adepanges/teamretro-mcp-server'

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