Skip to main content
Glama
rossumai

Rossum MCP Server

Official
by rossumai

rossum_get_queues

Retrieve all document processing queues from your Rossum organization to analyze workflow status and structure.

Instructions

Get all queues from the Rossum organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'rossum_get_queues' tool. It is registered via the @mcp.tool() decorator and delegates the core logic to _get_queues_impl().
    @mcp.tool()
    async def rossum_get_queues() -> List[Dict[str, Any]]:
        """Get all queues from the Rossum organization."""
        return await _get_queues_impl()
  • Helper function that fetches all queues from the Rossum API using _rossum_unpaginated_request, selecting essential fields like id, name, url, schema, workspace, and status.
    async def _get_queues_impl() -> List[Dict[str, Any]]:
        """Get all queues with essential fields only, handling pagination."""
        summary_keys = [
            "id", 
            "name", 
            "url", 
            "schema", 
            "workspace", 
            "status", 
        ]
        return await _rossum_unpaginated_request("GET", "/queues", summary_keys=summary_keys)
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 states the tool retrieves data ('Get'), implying a read-only operation, but doesn't address critical aspects like authentication requirements, rate limits, pagination, error handling, or what 'all queues' entails (e.g., format, filtering). This leaves significant gaps for safe and effective use.

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 a single, direct sentence that efficiently conveys the core purpose without any fluff or redundant details. It is front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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 for effective tool use. It doesn't explain what 'queues' are in this context, the return format, potential limitations (e.g., large result sets), or error conditions. For a tool with zero structured metadata, more behavioral and output details are needed.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, avoiding redundancy. A baseline of 4 is applied since it doesn't add unnecessary information beyond the schema's completeness.

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 ('Get') and resource ('all queues from the Rossum organization'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'rossum_get_workspaces' or 'rossum_get_hooks' beyond the resource type, which prevents a perfect score.

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 'rossum_get_workspace' or 'rossum_get_hooks'. It lacks context about prerequisites, organizational scope, or any exclusions, leaving the agent to infer usage from tool names 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/rossumai/rossum-mcp-server'

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