mcp-server-worldquantbrain

Overview Schema Source Related Servers Discussions Admin

Log in to BRAIN

authenticate

Instructions

Tools log in on their own, so this is only needed to start or restart a biometric check. When
state is biometric_required, have the user open biometric_url, then call
complete_authentication.

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

Input Schema

Name	Required	Description	Default
`force`	No	Discard the saved session and log in again.

Output Schema

Name	Required	Description	Default
`state`	Yes
`user_id`	No
`next_step`	No
`biometric_url`	No
`expires_in_seconds`	No
`credentials_configured`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, but the description adds the important non-obvious behavior: a saved session may be silently reused, so calling this is not always a fresh login. It also discloses the biometric handshake flow and the state value that triggers it. Minor gap: it does not say what happens when credentials are missing or invalid.

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

Conciseness5/5

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

Two short paragraphs, front-loaded with the core action and immediately followed by the when-to-use condition and the follow-up call. Every sentence carries actionable information with no restatement of the name or schema.

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?

An output schema exists, so return values need no explanation. Given a single optional boolean parameter and simple annotations, the description covers what the tool does, when to call it, what state triggers the biometric branch, and which sibling to call next, which is everything an agent needs.

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% and the single `force` parameter is fully documented there ("Discard the saved session and log in again"). The description implies the same distinction via "reusing a saved session when it is still valid" but adds no syntax or edge-case detail beyond the schema, so the baseline 3 applies.

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 (log in) plus the key behavioral distinction: it reuses a saved session when still valid. It also scopes the tool to starting or restarting a biometric check, which separates it from the implicit login that other tools perform on their own.

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

Usage Guidelines5/5

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

Explicitly says when it is NOT needed ("Tools log in on their own") and the one condition that does select it (starting or restarting a biometric check). It then routes the agent forward: when state is biometric_required, open biometric_url and call complete_authentication, naming the exact sibling and ordering.

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