Skip to main content
Glama
informatics-isi-edu

Deriva MCP Server

Official

set_display_annotation

Set display annotations on tables or columns to control naming, tooltips, and null-value display. Stage changes locally and apply them with apply_annotations().

Instructions

Set the display annotation on a table or column.

The display annotation controls basic naming and display options. Changes are staged locally until apply_annotations() is called.

Args: table_name: Name of the table. column_name: Name of the column (optional). If provided, sets the annotation on the column; otherwise sets it on the table. annotation: The display annotation value. Set to null/None to remove.

Display Annotation Schema (tag:isrd.isi.edu,2015:display):

{
    "name": "string",           // Display name (mutually exclusive with markdown_name)
    "markdown_name": "string",  // Markdown-formatted name (mutually exclusive with name)
    "name_style": {
        "underline_space": true,  // Replace underscores with spaces
        "title_case": true,       // Apply title case
        "markdown": true          // Interpret as markdown
    },
    "comment": "string",        // Tooltip/description text
    "show_null": {              // How to display null values per context
        "*": true,              // true = show "No value", false = hide, "string" = custom
        "compact": false,
        "detailed": ""N/A""
    },
    "show_foreign_key_link": {  // Show FK as link per context
        "*": true,
        "compact": false
    }
}

Valid contexts for show_null/show_foreign_key_link:

  • "*" (all contexts)

  • "compact", "compact/select", "compact/brief", "compact/brief/inline"

  • "detailed"

Returns: JSON with status and the target (table or column).

Examples: # Set table display name set_display_annotation("Image", annotation={"name": "Images"})

# Set column display name
set_display_annotation("Image", "Filename", {"name": "File Name"})

# Set name style to replace underscores with spaces
set_display_annotation("Image", annotation={"name_style": {"underline_space": true}})

# Remove display annotation
set_display_annotation("Image", annotation=null)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annotationNo
table_nameYes
column_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description carries the full burden. It transparently discloses the staging behavior, the removal via null, mutual exclusivity of name fields, and valid contexts for nested options. This is rich behavioral information beyond what a schema could provide.

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 long but appropriately structured into sections: overview, args, schema, contexts, returns, examples. Every sentence earns its place, providing necessary detail for a complex tool without 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?

The description covers the full scope of the tool, including the annotation schema, valid contexts, return value, and examples. Despite the output schema existing, the description adds clarity on behavior and usage, making it fully complete for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description thoroughly explains all three parameters, including the optional column_name and the full annotation structure with an explicit JSON schema. Examples further clarify usage.

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 verb 'Set' and the resource 'display annotation on a table or column', making the primary function unambiguous. It also distinguishes itself from siblings like set_visible_columns and apply_annotations by focusing on the display annotation specifically.

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 provides useful context that changes are staged until apply_annotations() is called, implying the proper workflow. However, it does not explicitly name alternative tools or state when not to use this tool, leaving some room for an agent to infer the distinction from siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/informatics-isi-edu/deriva-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server