Skip to main content
Glama

get_components

Retrieve security components from Devici with paginated results for threat model management.

Instructions

Get components from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'get_components'. Decorated with @mcp.tool() to register and execute the tool logic by calling the API client.
    @mcp.tool()
    async def get_components(limit: int = 20, page: int = 0) -> str:
        """Get components from Devici with pagination"""
        async with create_client_from_env() as client:
            result = await client.get_components(limit=limit, page=page)
            return str(result)
  • Supporting API client method that performs the actual HTTP GET request to the Devici API endpoint /components/ to retrieve components with pagination.
    async def get_components(self, limit: int = 20, page: int = 0) -> Dict[str, Any]:
        """Get all components."""
        params = {"limit": limit, "page": page}
        return await self._make_request("GET", "/components/", params=params)
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 of behavioral disclosure. It mentions 'with pagination', which hints at a list operation with pagination behavior, but fails to describe other critical traits such as whether this is a read-only operation, any authentication requirements, rate limits, or what the output looks like. For a tool with no annotations, this is a significant gap in transparency.

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 a single, efficient sentence that is front-loaded with the core action ('Get components from Devici') and includes an additional detail ('with pagination'). There is no wasted verbiage, making it appropriately concise for a basic tool, though it could be more structured with clearer separation of purpose and behavior.

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?

Given the tool's moderate complexity (2 parameters, no annotations, but has an output schema), the description is incomplete. It covers the basic purpose and hints at pagination but lacks details on parameter semantics, usage guidelines, and behavioral traits. The presence of an output schema mitigates the need to describe return values, but other gaps remain, making it only minimally adequate.

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

Parameters2/5

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

The input schema has 2 parameters (limit and page) with 0% description coverage, meaning the schema provides no semantic details. The description mentions 'with pagination', which loosely relates to the parameters but doesn't explain what 'limit' and 'page' mean, their units, default values, or valid ranges. It adds minimal value beyond the bare schema, insufficient to compensate for the low coverage.

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

Purpose3/5

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

The description states the action ('Get') and resource ('components from Devici'), which provides a basic purpose. However, it doesn't distinguish this tool from sibling tools like 'get_component' (singular) or 'get_components_by_canvas', leaving ambiguity about scope and differentiation. The mention of 'with pagination' adds some specificity but is insufficient for clear sibling differentiation.

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 'get_component' (for a single component) or 'get_components_by_canvas' (for filtered retrieval), nor does it specify prerequisites or contexts for usage. The lack of explicit when/when-not statements leaves 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/sdelements/devici-mcp'

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