Skip to main content
Glama
rossumai

Rossum MCP Server

Official
by rossumai

rossum_get_workspace

Retrieve a specific Rossum workspace by its ID to access workspace details and configuration for analysis purposes.

Instructions

Get a specific workspace by its ID.

Args: workspace_id: The ID of the workspace to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYes

Implementation Reference

  • The main handler function for the 'rossum_get_workspace' tool. It is registered via the @mcp.tool() decorator and delegates the API call to the internal _get_workspace_impl helper.
    @mcp.tool()
    async def rossum_get_workspace(workspace_id: str) -> Dict[str, Any]:
        """Get a specific workspace by its ID.
        
        Args:
            workspace_id: The ID of the workspace to retrieve
        """
        return await _get_workspace_impl(workspace_id=workspace_id)
  • Helper function that performs the actual HTTP GET request to the Rossum API to retrieve the specific workspace by ID.
    async def _get_workspace_impl(workspace_id: str):
        """Get a specific workspace by ID"""
        return await _rossum_request("GET", f"/workspaces/{workspace_id}")
  • Core utility function for making authenticated HTTP requests to the Rossum API, used by workspace retrieval.
    async def _rossum_request(method: str, path: str, **kwargs) -> Any:
        """Make a request to the Rossum API"""
        try:
            response = await client.request(
                method=method,
                url=f"{ROSSUM_API_BASE}{path}",
                headers=await get_rossum_headers(),
                **kwargs
            )
            response.raise_for_status()
            
            # Handle cases where Rossum might return empty body on success (e.g., 204)
            if response.status_code == 204:
                return None 
            return response.json()
        except httpx.HTTPStatusError as e:
            # Get error detail from response if possible
            error_detail = str(e)
            try:
                error_detail = e.response.json()
            except Exception:
                pass
            raise Exception(f"Rossum API error {e.response.status_code}: {error_detail}")
        except httpx.RequestError as e:
            raise Exception(f"Rossum API request failed: {str(e)}")
  • Helper to generate authentication headers for Rossum API requests.
    async def get_rossum_headers() -> Dict[str, str]:
        return {
            "Authorization": f"Token {ROSSUM_API_KEY}",
            "Content-Type": "application/json"
        }
Behavior2/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 states the tool retrieves a workspace, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling (e.g., what happens if the ID is invalid), or response format. This is a significant gap for a tool with no annotation coverage.

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 appropriately sized and front-loaded: the first sentence clearly states the purpose, and the 'Args' section efficiently documents the parameter. There is no wasted text, and every sentence adds value by either explaining the tool or its parameters.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks context on authentication, error handling, response structure, and usage relative to siblings. While concise, it doesn't provide enough information for an agent to confidently invoke the tool without additional assumptions.

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 adds meaning by specifying that 'workspace_id' is 'The ID of the workspace to retrieve,' which clarifies the parameter's purpose beyond the schema's title ('Workspace Id'). However, it doesn't provide details like format, constraints, or examples, leaving gaps in parameter understanding.

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 tool's purpose: 'Get a specific workspace by its ID.' This specifies the verb ('Get') and resource ('workspace'), and distinguishes it from the sibling 'rossum_get_workspaces' (which retrieves multiple workspaces). However, it doesn't explicitly mention what 'workspace' means in this context or differentiate from other sibling tools like 'rossum_get_queues' beyond the resource type.

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 when to use 'rossum_get_workspace' instead of 'rossum_get_workspaces' (e.g., when you know the specific ID), nor does it reference other sibling tools like 'rossum_get_queues' for related resources. Usage is implied by the parameter requirement but not explicitly stated.

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