Skip to main content
Glama

get_component

Retrieve a specific component by its ID to access detailed information within threat modeling resources.

Instructions

Get a specific component by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
component_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'get_component', registered via @mcp.tool(). It fetches the component using the API client and returns it 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)
  • The API client's get_component method, which makes the authenticated HTTP GET request to retrieve the specific component 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. It states 'Get' which implies a read operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or what happens if the ID doesn't exist. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, efficient sentence that front-loads the core action ('Get a specific component by ID') with zero wasted words. It's appropriately sized for a simple retrieval tool and doesn't include unnecessary details.

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 (single parameter, read operation) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and multiple sibling tools, it lacks context about the domain (e.g., threat modeling components) and differentiation, leaving the agent to rely heavily on the tool name and schema.

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 description adds meaning by specifying that the 'component_id' parameter is used to get a 'specific component', which clarifies the purpose of the single parameter. With 0% schema description coverage (the schema only has titles, no descriptions), this compensates well by explaining the parameter's role, though it doesn't detail format or constraints. For a tool with 1 parameter, this is sufficient.

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 context and doesn't differentiate from sibling tools like 'get_components' or 'get_components_by_canvas'. It provides basic purpose but lacks specificity about the domain or how it differs from related tools.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_components' (plural) and 'get_components_by_canvas', the description doesn't indicate that this tool is for retrieving a single component by its ID, nor does it mention prerequisites or exclusions. The agent must 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/geoffwhittington/devici-mcp'

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