Hustle Got Real

Post Virtualassistants Access

hgr_post_virtualassistants_access

Destructive

Dedicated HGRApi tool for POST api/VirtualAssistants/Access. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Activates, suspends or revokes one relationship without deleting products or historical authorship. ownerAgent: account-metrics. Use when: Resume accepted access, temporarily suspend or revoke it. Input: Id, current AccessVersion, AccessStatus: 2 active, 3 suspended, 4 revoked. Output: Acquiring an active slot when the account already has 3 active or invited VAs returns 409 va_profile_limit. Suspension/revocation remain available, free a slot, cancel outstanding invitations and block existing VA tokens; they do not reset email limits. Search terms: virtualassistants access. 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_access"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	HGRApi POST /api/VirtualAssistants/Access request body.
`confirmed`	Yes	Must be true after the user explicitly requested or confirmed the exact action.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations it discloses the concrete side effects of suspension/revocation (frees a slot, cancels outstanding invitations, blocks existing VA tokens, does not reset email limits) and the exact failure mode (409 when 3 active or invited VAs exist). It also states the confirmed=true execution gate, which is meaningful for a destructive operation.

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

Conciseness4/5

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

Front-loaded with endpoint and purpose, then use case, inputs, outputs, and search terms in a logical order with no filler paragraphs. Minor redundancy in the 'explicit tool with a fixed endpoint; it is not a generic endpoint caller' clause and the search-terms line.

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

Completeness5/5

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

For a destructive, open-world mutation with an output schema already supplied, the description covers triggers, status codes, side effects, error conditions, and the confirmation requirement. Nothing an agent needs to decide whether and how to call it is missing.

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

Parameters5/5

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

Although schema coverage is nominally 100%, the body parameter is an opaque description with no defined properties, so the description carries the real payload semantics: Id, current AccessVersion, and AccessStatus with numeric codes 2/3/4. That is genuine meaning the schema alone does not convey.

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 a specific verb set (activates, suspends, revokes) and resource (VA access relationship) and clarifies this is a fixed-endpoint wrapper, not a generic caller. It implicitly separates itself from hgr_post_virtualassistants_invite/acceptinvitation/permissions by describing lifecycle transitions, but it never names those siblings explicitly.

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?

The 'Use when: Resume accepted access, temporarily suspend or revoke it' line gives clear triggering conditions, and the 409 va_profile_limit note explains when suspension/revocation is still the right move. It lacks an explicit 'do not use this for X, use sibling Y instead' routing sentence.

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

All Hustle Got Real tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?