Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Sec Rolepermissions

sec_rolePermissions
Read-onlyIdempotent

List database-level permissions assigned to a Teradata role to reveal its access rights. Provide a role name to see the permissions granted to that role.

Instructions

List the database-level permissions granted to a named Teradata role. Use when the user asks what access rights a ROLE has, what a role is allowed to do, or what permissions have been granted to a role. Do NOT confuse with user-level queries — use sec_userDbPermissions for a user's direct permissions or sec_userRoles for a user's role membership. Requires a role name.

Arguments: role_name - Role 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
role_nameYesRole 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 / role_name / description
      Added value: +"Role name to analyze."
    • removedInput schema / properties / role_name / title
      Removed value: -"Role Name"
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / title
      Removed value: -"handle_sec_rolePermissionsArguments"
  3. First observed

TDQS

A4.3/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 useful behavioral context beyond annotations: it mentions the requirement for a role name and explains the persist behavior, including that it materializes a volatile table and returns the table name. This is a meaningful disclosure of the non-default behavior.

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 description is well-structured: purpose first, then usage guidance, then differentiation, then a brief parameter list. It is slightly longer than necessary because the arguments section duplicates the schema, but every non-duplicated sentence adds value and the key information is front-loaded.

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 two-parameter read-only tool with no output schema, the description provides enough context to select and invoke it correctly. It explains role-level scope, differentiates from user-level siblings, and covers the persist output behavior. It does not describe the default return format, but the verb 'List' plus the read-only annotations make the expected behavior reasonably clear.

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 the schema already documents both role_name and persist. The description repeats the same parameter meanings without adding significant new syntax, formatting, or edge-case information. Baseline 3 is appropriate because the schema carries the semantic load.

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: 'List the database-level permissions granted to a named Teradata role.' It clearly distinguishes itself from sibling tools sec_userDbPermissions and sec_userRoles by explicitly naming them and the difference between role-level and user-level queries.

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?

The description gives explicit when-to-use guidance ('Use when the user asks what access rights a ROLE has...') and explicit when-not-to-use guidance with named alternatives ('Do NOT confuse with user-level queries — use sec_userDbPermissions... or sec_userRoles...'). An agent can route correctly without inferring.

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