Skip to main content
Glama

get_component

Retrieve a specific security component by its ID to access threat model details within the Devici system.

Instructions

Get a specific component by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
component_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_component'. Registers the tool and implements the logic by calling the API client to retrieve a component by ID and returning the result as a string.
    @mcp.tool()
    async def get_component(component_id: str) -> str:
        """Get a specific component by ID"""
        async with create_client_from_env() as client:
            result = await client.get_component(component_id)
            return str(result)
  • Registration of the 'get_component' tool using the @mcp.tool() decorator on the handler function.
    @mcp.tool()
  • Helper function in API client that makes the HTTP GET request to fetch a specific component by ID from the Devici API.
    async def get_component(self, component_id: str) -> Dict[str, Any]:
        """Get specific component by ID."""
        return await self._make_request("GET", f"/components/{component_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 of behavioral disclosure. It states 'Get a specific component by ID', which implies a read-only operation, but doesn't cover critical aspects like authentication requirements, error handling (e.g., what happens if the ID is invalid), rate limits, or response format. This leaves significant gaps in understanding how the tool behaves beyond the basic action.

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 extremely concise with a single sentence ('Get a specific component by ID') that is front-loaded and wastes no words. It efficiently communicates the core action and key parameter, making it easy to parse quickly.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and incomplete parameter guidance, it lacks context on behavioral aspects like permissions or errors, making it incomplete for safe and effective use without additional inference.

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 mentions 'by ID', which adds meaning to the 'component_id' parameter in the input schema, but with 0% schema description coverage, it doesn't fully compensate. It doesn't specify the ID format (e.g., UUID, numeric), constraints, or examples, leaving the parameter only partially clarified beyond what the schema's title ('Component Id') provides.

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 'Get a specific component by ID' clearly states the action (get) and resource (component), but it's vague about what 'component' means in this domain and doesn't distinguish this tool from similar siblings like 'get_components' (plural) or 'get_components_by_canvas'. It provides basic purpose but lacks specificity about the component type or context.

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 offers no guidance on when to use this tool versus alternatives. With siblings like 'get_components' (for listing) and 'get_components_by_canvas' (for filtered retrieval), it doesn't explain that this is for fetching a single component by its unique identifier, leaving the agent to infer usage from 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/sdelements/devici-mcp'

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