Skip to main content
Glama
omilia

Omilia MCP Tools

Official
by omilia

get_collection_variables

Retrieve all variables from a specified collection in the Omilia Cloud Platform to manage and access dialog data.

Instructions

Get a list of all variables in a collection.

Args:
    collection_id: The ID of the collection to get variables for

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes

Implementation Reference

  • The MCP tool handler and registration for 'get_collection_variables'. It creates an EnvironmentsManagerClient and calls its get_collection_variables method.
    @mcp.tool()
    def get_collection_variables(collection_id: str) -> list[str]:
        """Get a list of all variables in a collection.
    
        Args:
            collection_id: The ID of the collection to get variables for
        """
        client = EnvironmentsManagerClient()
        return client.get_collection_variables(collection_id=collection_id)
  • The core implementation in EnvironmentsManagerClient that fetches variables from the API endpoint.
    def get_collection_variables(self, collection_id: str) -> dict:
        """Get a list of all variables in a collection."""
        endpoint = f"envs-manager/api/v1/variables-collections/{collection_id}"
        return self.get(endpoint)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action of getting a list, without mentioning whether this is a read-only operation, if it requires permissions, what format the list returns in, or any rate limits. This leaves significant gaps for a tool that likely interacts with collections.

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 appropriately sized with two sentences: one stating the purpose and another explaining the parameter. It's front-loaded with the main action, though the parameter explanation could be integrated more seamlessly. There's no wasted text, making it efficient.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the returned list looks like (e.g., structure, fields), any prerequisites like authentication, or how it differs from sibling tools. For a tool with one parameter but no structured context, this leaves too many unknowns for effective use.

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?

The schema description coverage is 0%, but the description compensates by explaining the single parameter 'collection_id' as 'The ID of the collection to get variables for'. This adds meaning beyond the schema's title 'Collection Id', though it doesn't detail format or constraints. With one parameter, this meets the baseline for minimal viability.

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 verb ('Get') and resource ('list of all variables in a collection'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_variable_collections', which could be a related alternative for finding collections rather than variables within one.

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. It doesn't mention sibling tools like 'search_variable_collections' or specify contexts where this tool is preferred, leaving the agent to infer usage based on the name alone.

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/omilia/mcp'

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