Skip to main content
Glama
WYRE-AI

avanan-legacy-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

avanan_create_msp_user

Create a new MSP user account and specify role, login options, data visibility, alert delivery, and weekly report preferences.

Instructions

Create a new MSP user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesUser role.
MSPIdNoParent MSPs only: create the user under this child MSP.
emailYesUser email address.
lastNameYesUser last name.
firstNameYesUser first name.
samlLoginYesAllow SAML login to the MSP portal.
sendAlertsYesSend customer tenant alerts to this user.
directLoginYesAllow password login to the MSP portal.
viewPrivateDataYesAllow the user to view private data on customer portals.
receiveWeeklyReportsYesSend weekly reports from customer tenants to this user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / properties / MSPId
      Added value: +{
+  "description": "Parent MSPs only: create the user under this child MSP.",
+  "type": "integer"
+}
  2. Addedv1.1.1
  3. Removedv1.1.0
  4. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only restates the creation operation. It does not mention permissions, idempotency, validation failures, whether an existing email causes an error, or any side effects beyond creating the user.

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, front-loaded sentence states the action and resource with no filler. Every word contributes to purpose clarity.

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 schema provides complete parameter semantics, so an agent can assemble the required fields. However, with no annotations and no output schema, the description omits behavioral context such as response behavior, error conditions, or permission requirements, leaving the definition only minimally complete for a complex create operation.

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 the input schema already documents all 10 parameters, including the role enum and MSPId constraint. The description adds no parameter-level detail, which is acceptable under the high-coverage baseline.

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 uses a specific verb ('Create') and a specific resource ('MSP user'), clearly distinguishing it from sibling operations like list/get/update/delete MSP users. There is no ambiguity about the tool's core function.

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?

The wording implies this tool is for creating a new MSP user, and the sibling names make alternatives (update/delete/get/list) evident. However, it does not explicitly state when to prefer this tool over those alternatives or mention prerequisites such as parent MSP authorization.

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