Skip to main content
Glama

Get Team Staff

get_team_staff
Read-only

Retrieve team staff for a given team ID, including role, level, specialty, and salary. Use it to review your own team's staff roster.

Instructions

Staff in your own team: role, level, specialty, salary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "get_team_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description must add value beyond that. It lists returned fields but says nothing about permissions, pagination, or whether the result is guaranteed to be the caller's team only; the output schema covers the return shape.

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

Conciseness3/5

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

It is short with no wasted words, but it is a noun phrase and field list rather than a structured statement of action, so the brevity comes at the cost of clarity.

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

Completeness2/5

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

For a tool with one required, completely undocumented parameter and an output schema, the description should at minimum explain what team_id identifies and how this differs from sibling roster/salary tools; it does neither.

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% for the single required parameter team_id, so the description carries the full burden and does not compensate at all: it never mentions team_id, its format, or how 'your own team' relates to passing an explicit ID.

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

Purpose3/5

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

The fragment 'Staff in your own team: role, level, specialty, salary' does convey the resource (team staff) and the fields returned, but it never states a verb and does not distinguish itself from close siblings like get_team_roster, get_team_salaries, or get_team.

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?

'in your own team' hints at a scope restriction, implying this is not for other teams, but it never says when to use this versus get_team_roster/get_team_salaries or what to do for another team's staff.

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