Skip to main content
Glama
lensesio

Lenses MCP Server

by lensesio

update_dataset_topic_description

Modify topic descriptions in Kafka metadata to improve data catalog clarity and maintain accurate documentation across environments.

Instructions

Update topic description (in metadata).

Args: environment: The environment name. topic_name: Name of the topic. description: The description of the topic. Returns: Success message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYes
topic_nameYes
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'update_dataset_topic_description' tool, decorated with @mcp.tool() for registration. It updates the description of a Kafka topic's dataset metadata via an API PUT request.
    @mcp.tool()
    async def update_dataset_topic_description(
        environment: str,
        topic_name: str,
        description: Optional[str] = None
    ) -> Dict[str, Any]:
        """
        Update topic description (in metadata).
        
        Args:
            environment: The environment name.
            topic_name: Name of the topic.
            description: The description of the topic.
        Returns:
            Success message.
        """
        # The description cannot be an empty string so if it is, replace with a null value
        description_payload = { "description": description if description else None }
    
        endpoint = f"/api/v1/environments/{environment}/proxy/api/v1/datasets/kafka/{topic_name}/description"
    
        return await api_client._make_request("PUT", endpoint, description_payload)
  • The @mcp.tool() decorator registers the update_dataset_topic_description tool with the MCP server.
    @mcp.tool()
  • Docstring providing input parameters and return type description, serving as schema documentation.
    """
    Update topic description (in metadata).
    
    Args:
        environment: The environment name.
        topic_name: Name of the topic.
        description: The description of the topic.
    Returns:
        Success message.
    """
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's an update operation but doesn't mention permission requirements, whether changes are reversible, rate limits, or what happens to existing descriptions. For a mutation tool with zero annotation coverage, this is insufficient.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence serves a purpose, though the 'Returns' section could be more informative beyond 'Success message'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no annotations, the description provides basic purpose and parameter identification. However, with an output schema present, the description doesn't need to detail return values. The main gap is lack of behavioral context for a write operation.

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 0%, so the description must compensate. It lists all three parameters with brief explanations, but doesn't provide format details, constraints, or examples. The description adds basic meaning but doesn't fully compensate for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update topic description') and specifies it's in metadata, which distinguishes it from other update operations. However, it doesn't explicitly differentiate from sibling tools like 'update_topic_metadata' or 'update_dataset_topic_tags', which could be related operations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'update_topic_metadata' or 'update_dataset_topic_tags'. It lacks context about prerequisites, typical scenarios, or exclusions for this specific metadata update operation.

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/lensesio/lenses-mcp'

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