Skip to main content
Glama

Post Virtualassistants Permissions

hgr_post_virtualassistants_permissions
Destructive

Dedicated HGRApi tool for POST api/VirtualAssistants/Permissions. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Updates the VA display name, replaces per-store grants and increments the access version. ownerAgent: account-metrics. Use when: Rename a VA or change their stores or permissions without sending an invitation or interrupting access. Input: Id, current AccessVersion, optional Name (1–50 nonblank characters), Stores. Omitting Name preserves the existing name. Output: Effective from the next request; 409 on conflicting edits. Preserves the email, credentials and access state. Search terms: virtualassistants permissions. Send the exact request payload in body. Requires confirmed=true before execution.

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": {
      "body": "<body>",
      "confirmed": "<confirmed>"
    },
    "name": "hgr_post_virtualassistants_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/VirtualAssistants/Permissions request body.
confirmedYesMust be true after the user explicitly requested or confirmed the exact action.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that per-store grants are replaced (the destructive surface), the access version is incremented, edits take effect from the next request, a 409 is returned on conflicting edits, and the email, credentials, and access state are preserved. It also documents the confirmation gate. This is exactly the context a destructive, non-idempotent tool needs.

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?

Useful content is front-loaded and dense, but several sentences are padding: the endpoint restatement, the 'not a generic endpoint caller' disclaimer, the 'HGRApi functional documentation' label, and the 'Search terms' line that merely repeats the tool name. Trimming the boilerplate would make the behavioral facts more prominent.

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 mutation tool with an output schema, the description covers what changes, what is preserved, concurrency conflicts, effect timing, and the confirmation requirement, so an agent can call it safely. The remaining gap is payload shape detail for the Stores grants, which an agent must still infer.

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?

Although the schema is nominally fully described, the required 'body' parameter is opaque in the schema; the description compensates by naming Id, current AccessVersion, optional Name, and Stores, and by giving the constraint (1-50 nonblank characters) and omission semantics (omitting Name preserves the existing name). The structure of the Stores collection is left unspecified.

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 functional summary gives a precise verb-and-resource statement: it renames the VA display name, replaces per-store grants, and increments the access version. The clause 'without sending an invitation or interrupting access' implicitly separates it from hgr_post_virtualassistants_invite, but the overlap with the sibling hgr_update_virtual_assistant is never addressed. The leading boilerplate ('Dedicated HGRApi tool for POST api/...', 'not a generic endpoint caller') restates the name rather than adding scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

An explicit 'Use when' clause states the trigger conditions: renaming a VA or changing stores/permissions without an invitation or access interruption. The confirmation prerequisite ('Requires confirmed=true before execution') is also stated. No explicit when-not condition or named alternative is given for the near-duplicate update tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources