Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

dba_sessionInfo

Read-onlyIdempotent

Report active session information for a specific user or all users. Identifies open connections and currently logged-in sessions.

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.9/5.0
Behavior5/5

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

The description discloses that persist=True materializes the result as a volatile table and returns the table name, adding behavioral context beyond the readOnlyHint and idempotentHint annotations. No contradiction with 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 two concise paragraphs: first explaining purpose and usage context, then listing parameters. Every sentence adds value; no redundancy.

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?

Given two parameters, no output schema, and annotations, the description fully covers the tool's behavior: when to use, parameter semantics, and side effects of persist. An agent can invoke it correctly.

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% with descriptions for both parameters. The description adds operational context, e.g., explaining the effect of persist=True and the use of '*' for all users, going beyond the schema.

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 it reports 'currently active session information' for a specific user or all users, which is a specific verb+resource combination. It distinguishes from sibling tools like dba_databaseSpace or dba_featureUsage by focusing on sessions.

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?

Explicitly says 'Use when the user asks about open connections, active sessions, or currently logged-in users.' Also provides guidance on default behavior with '*' and that no clarification is needed, making it easy for the agent to decide when to invoke.

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