Skip to main content
Glama
Sign In
Polydev

Polydev

Official
by polydev-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Sign in to Polydev

login

Authenticate with Polydev via browser and store the token locally, avoiding manual copying; in sandboxed environments, provide a user_token instead.

Instructions

Sign in to Polydev in your browser and save the token on this machine, so you do not copy it by hand. In sandboxes without a browser, pass user_token instead.

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

Input Schema

NameRequiredDescriptionDefault
user_tokenNoPolydev token (pd_...). Use this where browser login is unavailable (sandboxes, containers). Get one at https://www.polydev.ai/dashboard/mcp-tokens
open_browserNoWhether to automatically open the browser (default: true)
timeout_secondsNoHow long to wait for authentication (default: 300 = 5 minutes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the mutation and network profile is known. The description adds useful context beyond that — it opens a browser, persists a token to the local machine, and implies a blocking wait — but never mentions the timeout window or what state a failure leaves behind. With annotations carrying the safety profile, this is solid but not rich.

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 sentences, zero waste. The primary browser flow comes first and the fallback follows, which matches the order an agent needs them.

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?

There is no output schema, so the description should say what a successful call yields; it covers persistence of the token but not the return payload or the blocking/timeout behavior implied by the 300-second default. For a simple three-parameter auth tool that is a small gap rather than a blocker.

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 coverage is 100%, so user_token, open_browser and timeout_seconds are all documented with defaults and bounds in the schema itself. The description only reinforces the user_token case already stated there, adding no new syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource (sign in to Polydev) and adds the side effect that distinguishes it: the token is saved locally so it need not be copied by hand. It does not name the closely related sibling get_auth_status, so an agent must infer the split between signing in and checking status.

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 a concrete conditional branch: in browserless sandboxes, pass user_token instead of using the browser flow. That is real routing guidance. It stops short of saying when not to call this at all (e.g., when a token is already stored — get_auth_status would answer that).

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

Deploy Server

Other Tools