Skip to main content
Glama
Sign In

agentView

by de.agentview
OverviewDiscussionsAdmin

Get Auth Session

get_auth_session
Idempotent

Polls a login session created by create_auth_session until the user completes the browser login. Poll every 2-3 seconds while status is 'pending'. Status 'active' reports the GRANTED scope, read back from the issued token. Completing the login does NOT authenticate this MCP session: pass session_request_id on every protected call afterwards. Omit it and the server falls back to your connector's bearer token, which usually carries content scope only, so content tools keep working while admin tools like pair_by_code refuse with admin_scope_required. The raw token is intentionally not returned over MCP. 'expired' means start over with create_auth_session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_request_id": "<session_request_id>"
    },
    "name": "get_auth_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_request_idYesThe sessionRequestId string returned by create_auth_session. Must be passed exactly as received.

Output Schema

NameRequiredDescriptionDefault
scopeNo
statusNo
expiresInNo
requestedScopeNo
tokenExpiresAtNo
sessionRequestIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / expiresIn / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / requestedScope / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / scope / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / sessionRequestId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / tokenExpiresAt / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / sessionRequestId
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / token
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "expiresIn": {
+      "type": "integer"
+    },
+    "requestedScope": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "pending",
+        "active",
+        "expired"
+      ],
+      "type": "string"
+    },
+    "token": {
+      "type": "string"
+    },
+    "tokenExpiresAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With annotations already signaling readOnlyHint=false and idempotentHint=true, the description adds substantial behavioral context: the raw token is intentionally not returned over MCP, completing login does NOT authenticate the MCP session, status 'active' reports the GRANTED scope read back from the token, and the fallback credential behavior with scope differences between content and admin tools. No contradiction with annotations — it enriches them.

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 dense (~120 words) but every sentence carries distinct, high-value information: purpose, polling cadence, status semantics, auth caveat, fallback behavior, security disclosure, and lifecycle handling. There is no filler, redundancy, or restatement of the schema. The length is fully justified by the tool's behavioral complexity.

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?

The tool has an output schema, so return values need no description-level coverage. The description covers all the remaining contextual needs: the orchestration relationship with create_auth_session, polling cadence, all three status outcomes (pending/active/expired) with appropriate actions, security constraints, and the critical downstream requirement to pass session_request_id on protected calls. Nothing an agent needs to invoke this correctly 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?

Schema coverage is 100% and the schema description already says 'Must be passed exactly as received.' The tool description adds value beyond that by explaining where the ID comes from (create_auth_session), how it must be reused on every protected call, and what happens if omitted. This is genuine complementary information, not schema repetition.

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 a specific verb and resource: "Polls a login session created by create_auth_session until the user completes the browser login." This clearly distinguishes the tool from its siblings (create_auth_session creates, this polls; authenticate is a different auth path) and states the terminal condition precisely.

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?

Explicit operational guidance is given: poll every 2-3 seconds while status is 'pending', start over with create_auth_session on 'expired', and pass session_request_id on every protected call afterwards. It also explains the consequence of omitting the parameter (fallback to the connector's bearer token) and which tool category that breaks (admin tools like pair_by_code). This is exemplary when-to-use-and-how guidance.

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

All agentView 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