Skip to main content
Glama
Sign In

Realmint

by io.github.realmint-io
OverviewDiscussionsAdmin

realmint_logout

Idempotent

Sign out note: Realmint keeps no signing session — server-side signing is your standing Privy delegation. To fully revoke it, go to app.realmint.io/mcp/delegate. Disconnecting the connector ends this session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses a critical behavioral trait: Realmint keeps no persistent signing session and that server-side signing is a standing Privy delegation. It warns that simply disconnecting only ends the current session and does not revoke delegation, which is essential for the user to understand real-world consequences. This goes well beyond the idempotent and destructive hints provided by annotations.

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?

The description is exceptionally compact: three short sentences, with the 'Sign out note' header immediately signaling the topic. Every sentence provides essential information—no filler or redundancy—and the line break improves readability.

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, session-ending tool with an output schema, the description is fully complete. It explains the action, the limitation, and the exact user path for full revocation. The annotations cover safety (idempotent, non-destructive), and the output schema covers return values, so no relevant behavioral detail is missing.

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 input schema has zero parameters, so there is no parameter semantics to add. Per the zero-parameter baseline, a score of 4 is appropriate, and the description's caveat about the Revoke URL is more relevant than any parameter detail would be.

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 opens with 'Sign out note' and explicitly states the tool's effect: 'Disconnecting the connector ends this session.' It clearly identifies the action (signing out/disconnecting a session) for the Realmint resource, and its focus on session termination distinguishes it from all sibling tools. The caveat about no signing session further sharpens what the tool does and does not do.

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?

The description explicitly tells the user when this tool is insufficient: 'To fully revoke it, go to app.realmint.io/mcp/delegate.' This draws a clear line between the tool's limited session-ending behavior and full delegation revocation, providing decisive context for the agent to know when to use this tool versus the external alternative.

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

All Realmint toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources