Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_list_team

Read-only

Retrieves assignable team members with their IDs, names, and emails so tickets can be routed to the correct support agent.

Instructions

The people tickets can be assigned to (id, name, email).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the returned fields (id, name, email), which matters because there is no output schema, but it says nothing about scoping (current workspace? all teams?), result size, or pagination.

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?

A single short sentence with the identifying condition front-loaded and zero wasted wording. The field list is packed into a parenthetical rather than a separate sentence.

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

Completeness4/5

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

For a zero-parameter, read-only list tool with no output schema, the description covers what an agent most needs: who the records are and what fields come back. Only the scope of 'team' (whose team, how large) remains unstated.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to convey. The baseline of 4 applies; the parenthetical field list describes outputs, not inputs.

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 names the resource precisely as 'the people tickets can be assigned to' and even lists the returned fields (id, name, email), which lets an agent tell it apart from avarole_list_calls or avarole_ticket_stats. It stops short of an explicit verb such as 'list', so it reads more as a resource definition than an action statement.

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?

Usage is only implied: the phrase 'people tickets can be assigned to' hints that this is the lookup to run before assigning a ticket. There is no explicit when-to-use, no exclusions, and no reference to the sibling avarole_list_agents or avarole_team_workload, which an agent may reasonably confuse with this tool.

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