Hustle Got Real

Post Virtualassistants Acceptinvitation

hgr_post_virtualassistants_acceptinvitation

Destructive

Dedicated HGRApi tool for POST api/VirtualAssistants/AcceptInvitation. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Verifies the invitation and recipient's own credentials, creating an independent Identity account when necessary. ownerAgent: account-metrics. Use when: Accept an emailed VA invitation. Input: Token, matching Email, own Password; existing accounts must provide their current password. Output: Links the identity and activates this relationship. Search terms: virtualassistants acceptinvitation. 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_acceptinvitation"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	HGRApi POST /api/VirtualAssistants/AcceptInvitation 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.2/5.0

Behavior4/5

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

Beyond the annotations (destructive=true, idempotent=false, openWorld=true), the description discloses that an independent Identity account may be created, that credentials are verified, that the effect is linking an identity and activating a relationship, and that confirmed=true must be set first. It adds real mutation-impact context rather than restating the flags.

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?

The purpose and gating constraint are front-loaded, but there is filler: "Dedicated HGRApi tool for POST ..." plus "it is not a generic endpoint caller" and a raw "Search terms:" line consume space without helping an agent decide or call. Roughly a third of the text is boilerplate.

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 destructive, confirmation-gated mutation with an output schema already present, the description covers the trigger, the credential requirements, the side effect on identity, and the confirmation prerequisite. Only minor gaps remain (no mention of error behavior for invalid or mismatched tokens), which is acceptable given the output schema carries return shape.

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 schema's body parameter is only described as "request body," so the description earns credit by enumerating the payload contents: Token, matching Email, and own Password, with the current password required for existing accounts. The confirmed gate is also explained in prose as an explicit-confirmation requirement, adding meaning beyond the flag's type.

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 names the exact verb and resource (POST api/VirtualAssistants/AcceptInvitation) and states the business action: verifying an invitation and recipient credentials, creating an Identity account if needed, and activating the relationship. That distinguishes it from adjacent siblings such as hgr_post_virtualassistants_invite, _login, and _access without opening any schema.

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?

It gives an explicit trigger ("Use when: Accept an emailed VA invitation") and states a precondition (existing accounts must supply their current password). It does not point at the sibling to use instead when the caller lacks a token or wants to send rather than accept an invitation, so the when-not half is missing.

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?