Skip to main content
Glama

Sign in to Todrawn

todrawn_login

Connects an agent to a person's Todrawn account so board tools can run. Returns the signed-in user or a link and code to approve the connection, then retry.

Instructions

Connects this agent to the person's Todrawn account so the board_* tools work. If already signed in it says as whom. Otherwise it returns a link and a code: ask the person to open the link and approve the connection, then retry. Sign-in finishes by itself in the background once they approve. The Scribe video tools need no sign-in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, open-world, non-idempotent, non-destructive). The description adds the genuinely useful behavior: it returns an existing identity if already signed in, otherwise a link plus code, and completion happens asynchronously in the background once the human approves — which explains why a retry is needed rather than a synchronous success.

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?

Four short sentences, front-loaded with the outcome and the board_* dependency, then the two response branches, then the exclusion. Every sentence carries distinct information and there is no filler.

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?

With no output schema and no parameters, the description carries the full burden and discharges it: both return branches (identity vs. link+code) and the async approval flow are described. An agent knows exactly what to do and say to the user after each outcome.

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?

The tool takes zero parameters, so there is no parameter semantics to add; baseline applies. The description correctly spends no words on a non-existent input schema and instead documents the human-interaction protocol.

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 — connecting the agent to the person's Todrawn account — and immediately explains the dependency that makes it matter (the board_* tools need it). It also distinguishes itself from the Scribe tools, which need no sign-in, so an agent can place it among siblings without opening any schema.

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?

Gives explicit when-to-use (to make board_* tools work), the already-signed-in case, the not-signed-in path with the retry instruction after the user approves, and an explicit exclusion (Scribe video tools need no sign-in). Nothing about selection or sequencing is left to inference.

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