Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Sec Userdbpermissions

sec_userDbPermissions
Read-onlyIdempotent

Lists database-level access permissions (SELECT, INSERT, UPDATE, DELETE, etc.) granted directly to a specific Teradata user across all databases. Shows what a user can do in each database.

Instructions

List the database-level access permissions (SELECT, INSERT, UPDATE, DELETE, etc.) granted directly to a specific Teradata user across all databases. Use when the user asks what a named user can DO in each database — their access rights, grants, or privileges on database objects. Do NOT use to see what roles a user has — use sec_userRoles for that. Requires a user name.

Arguments: user_name - User name to analyze. 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_nameYesUser name to analyze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+}
    • addedInput schema / properties / user_name / description
      Added value: +"User name to analyze."
    • removedInput schema / properties / user_name / title
      Removed value: -"User Name"
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / title
      Removed value: -"handle_sec_userDbPermissionsArguments"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description adds useful context by clarifying that only directly granted permissions are included. It also discloses the persist behavior: materializing to a volatile table and returning a table name. It does not detail the exact return fields, but the read-only annotation and list semantics reduce that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main purpose and usage guidance are front-loaded, and the description is compact enough for an agent to parse quickly. The argument list is somewhat redundant with the schema, but it is short and not distracting.

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 description is sufficient for this tool: it has simple parameters, full schema coverage, read-only/idempotent annotations, and no output schema. It covers scope, alternatives, and the persist behavior. It could be more explicit about the non-persist return format, but that is a minor gap given the clarity of the main action.

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?

The input schema covers both parameters completely, each with a clear description. The description's argument section repeats the schema descriptions without adding extra meaning, defaults, validation details, or examples beyond what is already present.

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 ('List'), a clear resource ('database-level access permissions'), and a precise scope ('granted directly to a specific Teradata user across all databases'). It also distinguishes itself from sec_userRoles by explicitly noting that it is not for viewing roles.

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 provides explicit when-to-use guidance: 'Use when the user asks what a named user can DO in each database.' It also gives a direct exclusion and alternative: 'Do NOT use to see what roles a user has — use sec_userRoles for that.'

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