Skip to main content
Glama
Midas-MCP

Midas-MCP

get_session_status

Read-only

Check whether the Midas session is active and when the refresh token expires, without triggering login or phone approval. Call it first when no sign-in is wanted.

Instructions

Midas oturumunun açık olup olmadığını ve refresh_token bitişini döner. Hiçbir koşulda giriş başlatmaz, telefona onay bildirimi göndermez. status: logged-in, logged-out ya da starting (giriş sürüyor). Diğer araçlar oturum kapalıyken giriş başlatır; giriş istenmiyorsa önce bunu çağır.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the critical negative behaviors: it never starts a login and never sends an approval push to the phone, which is exactly the side effect an agent must reason about given the siblings. It also enumerates the possible status values returned.

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: purpose first, then the negative-behavior guarantee, then the return values, then the usage rule. No sentence is redundant or buried.

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?

A no-parameter, no-output-schema read tool is fully covered: purpose, side-effect guarantees, status vocabulary, and routing advice are all present, leaving nothing an agent needs unclear.

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?

There are zero parameters, so the baseline is 4, and the description uses the space instead to explain the returned status vocabulary (logged-in, logged-out, starting), which the absent output schema would otherwise leave undefined.

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 and resource (returns whether the Midas session is open plus refresh_token expiry) and explicitly contrasts with other tools that start a login when the session is closed. An agent can distinguish it from the listed 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?

It gives an explicit when-to-use rule: other tools initiate login while the session is closed, so call this first if login is not wanted. Both the trigger condition and the reason (avoiding an unwanted side effect) are spelled out.

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