Skip to main content
Glama
informatics-isi-edu

Deriva MCP Server

Official

set_column_display

Set a column's display annotation to customize value rendering with number formats, boolean labels, and markdown patterns.

Instructions

Set the column-display annotation on a column.

Controls how a column's values are rendered, including custom formatting and markdown patterns.

Changes are staged locally until apply_annotations() is called.

Args: table_name: Name of the table containing the column. column_name: Name of the column. annotation: The column-display annotation value. Set to null/None to remove.

Column-Display Annotation Schema (tag:isrd.isi.edu,2016:column-display):

{
    "*": {                                    // Default for all contexts
        "pre_format": {
            "format": "%.2f",                 // printf-style format string
            "bool_true_value": "Yes",         // Display for true
            "bool_false_value": "No"          // Display for false
        },
        "markdown_pattern": "**{{{value}}}**",  // Markdown template
        "template_engine": "handlebars",        // or "mustache"
        "column_order": false                   // Disable sorting, or specify sort
    },
    "compact": {...},                         // Compact/list view options
    "detailed": {...},                        // Detailed/record view options
    "entry": {...},                           // Entry form options
    "entry/create": {...},                    // Create form options
    "entry/edit": {...}                       // Edit form options
}

Available options:

  • pre_format: Pre-processing before display

    • format: printf-style format (e.g., "%.2f" for 2 decimal places)

    • bool_true_value: Text to show for boolean true

    • bool_false_value: Text to show for boolean false

  • markdown_pattern: Template using {{{column_name}}} substitution

  • template_engine: "handlebars" (default) or "mustache"

  • column_order: Sort configuration or false to disable sorting

Template variables in markdown_pattern:

  • {{{_value}}} or {{{value}}}: The column's value

  • {{{_row.column_name}}}: Another column's value from same row

  • {{{$fkeys.schema.fkey.values.column}}}: Value from related table

Returns: JSON with status and the target column.

Examples: # Format numbers with 2 decimal places set_column_display("Measurement", "Value", { "*": {"pre_format": {"format": "%.2f"}} })

# Display boolean as Yes/No
set_column_display("Subject", "Active", {
    "*": {
        "pre_format": {
            "bool_true_value": "Active",
            "bool_false_value": "Inactive"
        }
    }
})

# Custom markdown pattern
set_column_display("Image", "URL", {
    "detailed": {
        "markdown_pattern": "[![Image]({{{_value}}})]({{{_value}}})"
    }
})

# Disable column sorting
set_column_display("Subject", "Notes", {
    "*": {"column_order": false}
})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annotationNo
table_nameYes
column_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that changes are staged locally until apply_annotations() is called, that null removes the annotation, and that it returns JSON with status. It also documents the annotation schema and template variables, though it omits permission and failure details.

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 warranted given the complex annotation parameter. It is logically structured with headers, a JSON schema, options, template variables, returns, and multiple examples. The main purpose is front-loaded.

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?

For a tool with a deeply nested annotation object, the description is comprehensive: it covers the schema, all available options, template variables, return behavior, and provides practical examples. Since an output schema exists, detailed return documentation is unnecessary.

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?

Schema description coverage is 0%, but the description provides an Args section explaining each parameter and an extensive, well-structured breakdown of the annotation object with examples. It explicitly states the null-means-remove behavior and details all options and template variables.

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 sets the column-display annotation on a column and controls rendering. It uses a specific verb+resource and distinguishes from siblings like set_column_description or set_display_name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for controlling column value rendering and mentions apply_annotations() as a required follow-up, but never explicitly compares to alternatives like set_display_annotation or says when not to use this tool.

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