mcp-server-worldquantbrain

by tukorama

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Finish a biometric login

complete_authentication

Completes authentication after the user passes the biometric check at biometric_url, finalizing the login session.

Instructions

Finish a login after the user completed the biometric check at biometric_url.

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

Input Schema

Name	Required	Description	Default
No arguments

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

A3.5/5.0

Behavior3/5

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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds the sequencing dependency on a prior biometric check, but says nothing about what the call returns, whether it is single-use, or how failures surface — meaningful gaps for a non-idempotent auth mutation.

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?

A single front-loaded sentence with no filler — the precondition is placed immediately after the action. It is efficient, though it is arguably too terse given the undefined biometric_url reference.

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?

An output schema exists, so return values need not be described, and with no parameters there is little else to document. The remaining gap is the unexplained provenance of biometric_url and the absence of any note about where in the auth sequence this call sits relative to its siblings.

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?

The tool takes zero parameters, so there is little schema semantics to add. However, the description introduces 'biometric_url' as if it were an input or a known handle, while the schema has no properties at all; an agent could reasonably wonder whether that value must be supplied, making the reference mildly ambiguous rather than clarifying.

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 gives a specific verb and resource ('Finish a login') plus the triggering condition ('after the user completed the biometric check'), which is enough to distinguish it from a plain authenticate call. It stops short of naming the sibling tool that produces the biometric step, so the two-step flow must be inferred.

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

Usage Guidelines3/5

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

It states the precondition for calling (biometric check already completed) but gives no exclusions, no mention of what to do if the check failed or timed out, and no pointer to the related auth tools such as authenticate or auth_status. Usage is implied rather than prescribed.

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