Skip to main content
Glama

Connect Rhylthyme account

login
Read-onlyIdempotent

For apps that cannot connect the Rhylthyme account directly: returns a sign-in URL, then accepts the pasted token. Only the user's own saved programs, runs and imports need it; everything public works without. Tokens last about an hour.

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
tokenNoThe token from the login page. Leave empty on the first call to get the sign-in URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / token / description
      Previous value: -"Paste the access token shown on the login page after you sign in. Leave empty on the first call to get the login URL."New value: +"The token from the login page. Leave empty on the first call to get the sign-in URL."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

The description adds real behavioral context beyond the annotations: the two-step URL-then-token flow and the ~1 hour token lifetime, which matters for retry planning. However, it never says whether the pasted token is stored, what happens on an invalid or expired token, or what the first call returns besides a URL, and 'accepts the pasted token' sits in mild tension with readOnlyHint=true, since establishing a session is a state change not a pure read.

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?

Three short sentences, front-loaded with the operating condition and the mechanism, with the token lifetime placed last where it is useful but non-blocking. Every clause carries information; nothing is repeated from the schema or annotations.

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?

For a single-optional-parameter auth tool with no output schema, the description covers when to use it, how the two-step exchange works, and how long credentials last. The remaining gap is what the tool returns on the first call (a URL plus anything else) and how failures surface, which an agent would otherwise have to discover empirically.

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% and the single optional parameter is already documented in the schema, including the 'leave empty on the first call' instruction. The description reinforces that sequencing by describing the URL-then-token flow, but adds no format, encoding, or error semantics for the token itself, so baseline 3 applies.

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 states a concrete mechanism: it returns a sign-in URL and then accepts a pasted token, which is more specific than the bare name 'login'. No sibling tool in the list performs authentication, so differentiation is implicit rather than stated, which keeps it just short of a 5.

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?

It gives an explicit when-to-use condition ('for apps that cannot connect the Rhylthyme account directly') and an explicit when-not ('everything public works without'), naming the exact resource classes (saved programs, runs, imports) that require it. An agent can decide whether to call this without opening any other tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.