Skip to main content
Glama
Sign In

~Alter

by com.truealter
OverviewDiscussionsAdmin

Invite to ~alter

invite_to_alter

Generate a URL inviting a person without an ~alter identity to register. Use this when you encounter someone not yet on ~alter and want to invite them. They claim a ~handle, confirm their email, and are done; identity is inferred from what they go on to do, never from a quiz. Returns invite_url (and assessment_url as a historical alias for the same value). callback_url is accepted and checked but not yet called. Once the person tells you their ~handle, alter_resolve_handle confirms it exists. Free L0.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "invite_to_alter"
  }
}

Input Schema

NameRequiredDescriptionDefault
referrerNoIdentifier of the referring agent/bot
callback_urlNoAccepted and checked, but not yet called

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, closed-world, and the description adds real context beyond them: the claim/email flow, the fact that callback_url is accepted but not yet invoked, the assessment_url alias, and the 'Free L0' cost tier. It does not disclose whether repeated calls mint duplicate or expiring invite URLs, which matters given idempotentHint=false.

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?

The core action and trigger are front-loaded and the sentence sequence is logical (what, when, flow, returns). The clause about identity being 'inferred from what they go on to do, never from a quiz' is rhetorical padding that does not help an agent decide or invoke.

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?

With no output schema, the description usefully names the returned invite_url and its assessment_url alias, plus the follow-up tool for confirming a handle. It leaves open invite expiry and duplicate-invite behavior, which are the main remaining unknowns for a non-idempotent generation tool.

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 both parameters are already documented; the description's note that callback_url is 'accepted and checked but not yet called' merely restates the schema text. The referrer parameter is never mentioned in the description, so no meaning is added beyond the structured fields.

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 opens with a specific verb plus resource: 'Generate a URL inviting a person without an ~alter identity to register.' The 'without an ~alter identity' qualifier implicitly separates it from agent-registration siblings like register_autonomous, but no sibling is named directly, which keeps it at a 4.

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 states an explicit trigger ('Use this when you encounter someone not yet on ~alter and want to invite them') and gives the exclusion condition (the person must lack an identity). It also routes the follow-up step to alter_resolve_handle once the ~handle is known, though it does not say what to do if the person already has an identity.

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

All ~Alter toolsInspect
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