Skip to main content
Glama

Get Team Member

team_get_member
Read-onlyIdempotent

Retrieve details for a specific team member by author ID or username from the configured team database, optionally scoped to a workspace, to support author lookup and team context.

Instructions

Get details about a specific team member. Requires TEAM_DB_PATH.

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": "team_get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorNoThe author ID/username to fetch
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
memberNo
detailsNoAdditional error context
successYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • removedInput schema / required
      Removed value: -[
      -  "author"
      -]
  2. First observedv9.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and a closed-world non-destructive profile, so the safety story is covered. The description adds a genuinely useful environmental prerequisite (TEAM_DB_PATH), but says nothing about what happens when the author is not found or how the member and workspace_id interact.

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

Conciseness4/5

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

Two short sentences, front-loaded with the purpose, with no filler or redundancy. It is efficient, though the brevity comes at the cost of the usage context noted elsewhere rather than from trimming waste.

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?

The tool is simple (2 optional params, rich annotations, and an output schema that explains return values), so much of the burden is already carried by structured fields. Still, a lookup tool sitting next to team_list_members and team_resolve_author should say when it is the right choice and what a missing member yields.

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%, and the schema already explains 'author' and the workspace isolation caveat about not using numeric project IDs. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 states a specific verb and resource ('Get details about a specific team member'), which is clearly distinct from team_list_members, team_add_member, and team_update_member_role. It stops short of explicitly contrasting with the closest sibling (listing members), but the singular/plural split is inferable from the name.

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 only guidance is the prerequisite 'Requires TEAM_DB_PATH.' There is no statement of when to prefer this over team_list_members for a single lookup, or over team_resolve_author when an author alias must be resolved first. The agent must infer the selection context.

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