Skip to main content
Glama
informatics-isi-edu

Deriva MCP Server

Official

set_table_display

Set table-display annotations to control row name patterns, page size, and row ordering. Changes are staged locally and applied with apply_annotations().

Instructions

Set the table-display annotation on a table.

Controls table-level display options like row naming patterns, page size, and row ordering.

Changes are staged locally until apply_annotations() is called.

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

Table-Display Annotation Schema (tag:isrd.isi.edu,2016:table-display):

{
    "row_name": {                              // How to display row identifiers
        "row_markdown_pattern": "{{{Name}}}",  // Template for row display
        "template_engine": "handlebars"        // or "mustache"
    },
    "detailed": {                              // Options for detailed view
        "hide_column_headers": true,           // Hide column headers
        "collapse_toc_panel": true             // Collapse table of contents
    },
    "compact": {                               // Options for compact/list view
        "page_size": 25,                       // Rows per page
        "row_order": [                         // Default sort order
            {"column": "RCT", "descending": true},
            "Name"
        ]
    },
    "*": {                                     // Default for all contexts
        "page_size": 10,
        "row_order": ["Name"]
    }
}

Context-specific options:

  • row_name: Special context for row identifier display

  • detailed: Detailed/record view

  • compact, compact/select, compact/brief: List views

  • *: Default for unspecified contexts

Available options per context:

  • row_order: Array of sort keys (column name or {column, descending})

  • page_size: Number of rows per page

  • collapse_toc_panel: Boolean to collapse TOC (detailed only)

  • hide_column_headers: Boolean to hide headers (detailed only)

  • row_markdown_pattern: Template string using {{{column}}} syntax

  • page_markdown_pattern: Template for entire page

  • separator_markdown: Separator between rows

  • prefix_markdown: Content before rows

  • suffix_markdown: Content after rows

  • template_engine: "handlebars" or "mustache"

Returns: JSON with status and the table name.

Examples: # Set row name pattern set_table_display("Subject", { "row_name": { "row_markdown_pattern": "{{{Name}}} ({{{Species}}})" } })

# Set default sort order and page size
set_table_display("Image", {
    "compact": {
        "row_order": [{"column": "RCT", "descending": true}],
        "page_size": 50
    }
})

# Configure detailed view
set_table_display("Page", {
    "detailed": {
        "hide_column_headers": true,
        "collapse_toc_panel": true
    }
})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annotationNo
table_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It transparently states that changes are staged and not applied immediately, and describes the return format. While permission requirements are not mentioned, the staging behavior is a key non-obvious trait that is disclosed.

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 long but well-structured with sections for Args, schema, options, and examples. Each part adds necessary context for complex configuration, though it could be slightly trimmed without losing value.

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 fully covers purpose, staging behavior, parameter semantics, annotation schema, context-specific options, and return value, with multiple examples. It is sufficiently complete for an agent to invoke the tool correctly, especially given the output schema exists.

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%, so the description fully compensates by documenting both parameters in Args and providing a detailed table-display annotation schema with available options and examples. This adds substantial meaning beyond the raw input 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 names the specific action ('Set the table-display annotation on a table') and clarifies its scope ('Controls table-level display options like row naming patterns, page size, and row ordering'). It clearly distinguishes from sibling tools like set_column_display and set_row_name_pattern by focusing on the table-display annotation resource.

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 explains that changes are staged locally until apply_annotations() is called, giving clear workflow context. It does not explicitly name alternative tools or exclusion conditions, but the examples and schema make the intended use apparent.

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