hypathesis

Initiate Device Auth

initiate_device_auth

Start a browser-based sign-in flow to get an API key for full access.

Call this when you need detailed analysis results (reasoning, measurements)
that require authentication. Returns a verification URL to show to the user.
After the user signs in, poll check_device_auth with the returned user_code
to get the API key.

Returns:
    {
      "verification_url": str,
      "user_code": str,
      "expires_in": 600,
      "message": str
    }

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior4/5

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

Discloses return values (verification URL, user_code, expires_in, message) and that it starts a sign-in flow. Annotations are neutral; no mention of side effects like invalidating previous auths.

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?

Description is brief: one sentence for purpose, two sentences for usage guidance, and a sample return. No unnecessary words.

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?

Tool has no parameters and a clear output; description covers the flow and return format completely, including subsequent step to poll check_device_auth.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters in input schema, so description does not need to add meaning. Schema coverage is 100% (empty schema is fully described by absence).

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 clearly states the tool starts a browser-based sign-in flow to get an API key for full access. It differentiates from sibling tools like check_device_auth (polling) and analysis tools.

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 'Call this when you need detailed analysis results that require authentication' and instructs to poll check_device_auth after user signs in.

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

All hypathesis tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0

Disambiguation5/5

Each tool has a distinct purpose: two for authentication flow (initiate, check), one for status polling, one for retrieving results. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (initiate_device_auth, check_device_auth, get_analysis_status, get_variable_relationships), making them predictable.

Tool Count5/5

Four tools is well-scoped for a focused service handling authentication, status checking, and result retrieval without unnecessary bloat.

Completeness3/5

The tools cover auth and retrieval but lack an upload tool, requiring external action to start the workflow. This is a notable gap for a complete lifecycle.

Resources

Need Help?