Skip to main content
Glama
rossumai

Rossum MCP Server

Official
by rossumai

rossum_get_schema

Retrieve a specific schema by its ID from the Rossum platform for analysis and integration purposes.

Instructions

Get a specific schema by its ID.

Args: schema_id: The ID of the schema to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schema_idYes

Implementation Reference

  • The main handler function for the 'rossum_get_schema' tool. It is registered using the @mcp.tool() decorator and delegates to the _get_schema_impl helper. Includes input schema via type hint (schema_id: str) and docstring.
    @mcp.tool()
    async def rossum_get_schema(schema_id: str) -> Dict[str, Any]:
        """Get a specific schema by its ID.
        
        Args:
            schema_id: The ID of the schema to retrieve
        """
        return await _get_schema_impl(schema_id=schema_id)
  • Helper function that performs the actual API request to retrieve the schema from the Rossum API using the generic _rossum_request function.
    async def _get_schema_impl(schema_id: str):
        """Get a specific schema by ID"""
        return await _rossum_request("GET", f"/schemas/{schema_id}")
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 it 'retrieves' a schema, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'retrieve' entails (e.g., returns JSON, includes metadata). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the main purpose in the first sentence. The 'Args' section is structured but could be more integrated; overall, it's efficient with little waste, though minor improvements in flow are possible.

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 complexity (simple retrieval), no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what a 'schema' entails in this context, the return format, or error cases, making it inadequate for reliable agent use without additional context.

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 description adds minimal semantics: it clarifies that 'schema_id' is 'The ID of the schema to retrieve'. With 0% schema description coverage and 1 parameter, this provides some value beyond the bare schema, but it's basic and doesn't detail format (e.g., numeric, string pattern) or constraints. Baseline is 3 as it compensates slightly for low coverage.

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 'a specific schema by its ID', making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'rossum_get_workspace' or 'rossum_get_queues' 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. It lacks context about prerequisites, such as needing a valid schema ID, or comparisons to sibling tools like 'rossum_get_workspaces' for listing schemas, leaving usage unclear.

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