Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.get_session

Retrieve a single session from a connected Clerk application by its session id.

Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account.

Returns session id, user_id, status, last_active_at, expire_at, client_id, created_at, and updated_at.

Cost = 3 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesClerk session id (sess_...) to retrieve or modify.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoClerk session id (sess_...).
statusNoCurrent status of the session.
user_idNoClerk user id (user_...) that owns this session.
client_idNoClerk client id associated with this session.
expire_atNoUnix timestamp in milliseconds when this session expires.
created_atNoUnix timestamp in milliseconds when the session was created.
updated_atNoUnix timestamp in milliseconds when the session was last updated.
last_active_atNoUnix timestamp in milliseconds of the last activity on this session.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses return fields and cost, and implies a read-only operation via 'Retrieve'. However, it does not mention error cases, permissions, or rate limits, which are relevant behavioral details.

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 compact and front-loaded, with four sentences covering purpose, prerequisites, return fields, and cost. Every sentence adds value without redundancy.

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 simple get operation, the description covers prerequisites, targeting, return fields, and cost. An output schema exists, so return format is documented. It lacks explicit error-handling notes but is otherwise complete for the tool's complexity.

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 description coverage is 100%, so baseline is 3. The description's note about clerk_instance_id largely repeats the schema's own explanation ('Omit to use the default connected account'), adding no significant new meaning beyond what is already in the parameters.

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 clearly states the tool retrieves a single session by ID, with a specific verb and resource. It distinguishes itself from siblings like list_sessions by emphasizing 'single session' and mentioning the connected Clerk application.

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?

Provides explicit prerequisite guidance to call clerk.get_connected_accounts first and explains how to target a specific connection or default. However, it does not explicitly contrast with alternatives like list_sessions or revoke_session, leaving some ambiguity about when to prefer this tool.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources