Skip to main content
Glama
Sign In
YotoMCP Local

YotoMCP Local

by steventswu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

yoto_auth_start

Start Yoto OAuth PKCE login by generating an authorization URL. Open the URL, then call yoto_auth_complete to finish authentication.

Instructions

Start Yoto Authorization Code + PKCE login. Open the returned URL, then call yoto_auth_complete.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide limited behavioral detail (openWorldHint=true, readOnlyHint=false), and the description adds that a URL is returned, must be opened, and requires calling yoto_auth_complete to finish. No contradiction with annotations was found.

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 that are front-loaded with the primary action and include the necessary next step. No filler or redundant detail.

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?

For a zero-parameter tool with no output schema, the description explains the returned URL and the required completion call, making the tool self-contained for an agent to invoke correctly.

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 has zero parameters, so description does not carry parameter responsibilities. Baseline 4 is appropriate; no supplemental parameter explanation is needed.

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 states a specific verb 'Start' and resource 'Yoto Authorization Code + PKCE login', and explicitly mentions the follow-up tool yoto_auth_complete, distinguishing it from siblings like yoto_auth_status or yoto_logout.

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?

It gives an explicit sequential workflow: open the returned URL, then call yoto_auth_complete. This is clear guidance, but it lacks explicit when-not conditions, such as whether to skip when already authenticated.

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