Skip to main content
Glama

AINDEX

Connect this chat to the person's AINDEX account

connect_account

Signs this chat in to the person's AINDEX account, so the agent tools work here: their agents, making one, funding it, its checks. Call with no code: it gives a link. The person opens it, signs in with their wallet (a new wallet makes a new account) and presses Allow; the page shows a six-digit code. Ask them for it and call again with code. Nothing in this chat can ever move money out of an agent.

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": "connect_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe six digits the page showed after Allow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations say this is non-read-only, non-destructive, non-idempotent, closed-world; the description adds real context beyond that: a new wallet creates a new account, the person must press Allow, and the reassurance that nothing in the chat can move money out of an agent. It leaves the consequence of re-calling with a stale code or re-connecting while already signed in undisclosed.

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-loads the purpose, then walks the two-step flow in order, ending on the safety guarantee. Dense and slightly run-on, but every clause carries either procedure or reassurance; nothing is filler.

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?

No output schema exists, so the description properly explains both return shapes (a link, then presumably a connected session) and the human-in-the-loop steps. Only gaps are failure modes — expired or wrong code, already connected — for what is otherwise a self-contained setup tool.

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?

Schema coverage is 100%, but the description still adds meaning the schema cannot: the code is the six digits shown after the person presses Allow, and omitting the parameter is a meaningful first step rather than an incomplete call. That is genuine value beyond the maxLength=20 string definition.

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?

States a specific verb and resource ('signs this chat in to the person's AINDEX account') and immediately names what it unlocks — agents, creating one, funding it, its checks — which ties it to siblings like create_agent and agent_funding without ambiguity.

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?

Gives an explicit two-call sequence: call with no code to get a link, then call again with the six-digit code. It tells the agent what to ask the person for, but never states prerequisites (existing session, what happens if already connected) or a boundary against other tools.

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