Skip to main content
Glama
Sign In
adtk

adtk

by zach-snell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

manage_users

Find and retrieve Azure DevOps users. Search by display name or email, or get the current user.

Instructions

Search and get Azure DevOps users. Actions: 'get_current', 'search'

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": {
      "action": "<action>"
    },
    "name": "manage_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform: 'get_current', 'search'
queryNoSearch query - display name or email (for search)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as read-only nature, authentication requirements, or response details. With no annotations, the description fails to inform the agent about side effects or constraints beyond the listed actions.

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 very concise with two sentences, front-loading the purpose and key actions. Every word adds value, and there is no unnecessary text.

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 simplicity of the tool (2 parameters, no output schema), the description provides the core information but lacks details on return values or behavior of each action, leaving some ambiguity for an AI agent.

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%, so baseline is 3. The description repeats the action names already in the schema without adding new semantic meaning or usage tips for the parameters.

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

Purpose5/5

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

The description clearly states 'Search and get Azure DevOps users' with specific actions listed. It distinguishes from sibling tools by specifying the resource (users) as opposed to other entities like attachments or pipelines.

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?

No guidance is provided on when to use 'get_current' vs 'search', nor any context about alternatives or prerequisites. The description only lists available actions without explaining their appropriate contexts.

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