Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Dba Sessioninfo

dba_sessionInfo
Read-onlyIdempotent

Identify currently active database sessions and logged-in users for a specified user or all users, helping you monitor open connections and session activity.

Instructions

Report currently active session information for a specific user or all users. Use when the user asks about open connections, active sessions, or currently logged-in users. You may call with the default '*' to show all sessions when no specific user is mentioned — no clarification required for this tool.

Arguments: user_name - User name to analyze. Use '*' to get all users. persist - If True, materializes result as a volatile table and returns table name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persistNoIf True, materializes result as a volatile table and returns table name
user_nameNoUser name to analyze. Use '*' to get all users.*

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedInput schema / properties / user_name / description
      Previous value: -"User name to analyze. User '*' to get all users."New value: +"User name to analyze. Use '*' to get all users."
  2. Changed3 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / persist
      Added value: +{
+  "default": false,
+  "description": "If True, materializes result as a volatile table and returns table name",
+  "type": "boolean"
+}
    • removedInput schema / properties / user_name / title
      Removed value: -"User Name"
  3. Changed4 schema fields changedv1.0.0
    • addedInput schema / properties / user_name / default
      Added value: +"*"
    • addedInput schema / properties / user_name / description
      Added value: +"User name to analyze. User '*' to get all users."
    • removedInput schema / required
      Removed value: -[
-  "user_name"
-]
    • removedInput schema / title
      Removed value: -"_dynamic_toolArguments"
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds meaningful behavioral context beyond that, particularly the persist behavior: materializing results as a volatile table and returning the table name. This is a real side effect the agent should know. It could mention output format details, but the added context is solid.

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: a clear purpose statement, a usage trigger, a default-behavior note, and a minimal Arguments block. Every sentence earns its place and there is no filler or duplication beyond the necessary parameter repetition.

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?

The tool is simple, has only two optional parameters, full schema coverage, and safety annotations. The description covers purpose, usage triggers, defaults, and the persist side effect. The only notable gap is that no output shape is described despite there being no output schema, but this is minor for a reporting tool of this simplicity.

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%, and the input schema already documents both parameters fully. The description repeats the same parameter explanations, adding no new semantic meaning beyond usage context. This meets the baseline for fully schema-documented 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 states a specific verb ('Report') and resource ('currently active session information for a specific user or all users'). This clearly differentiates it from sibling DBA tools like dba_userSqlList or dba_tableSpace, which target different resources.

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?

The description explicitly defines when to use the tool: 'when the user asks about open connections, active sessions, or currently logged-in users.' It also gives guidance on the default '*' behavior and states that no clarification is required. It lacks explicit when-not-to-use or alternative tool routing, so it falls just short of a 5.

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

Deploy Server

Other Tools