Skip to main content
Glama
Sign In
solibri

solibri

by Vanderjohnny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Mostrar componente

solibri_show_component_info

Select an IFC component by its 22-character GUID and open its information window in Solibri for detailed inspection.

Instructions

Seleciona um componente pelo GUID IFC e abre a janela de informacoes dele no Solibri.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guid": "<guid>"
    },
    "name": "solibri_show_component_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYesGUID IFC do componente, com 22 caracteres.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false and openWorldHint=true, so the description doesn't need to restate those. It adds that it selects a component and opens an info window, which gives some behavioral context beyond annotations. However, it doesn't mention side effects like changing selection state or error behavior. With annotations covering the basic traits, this is adequate but not rich.

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, front-loaded sentence with no filler words. It immediately states the action and target. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description adequately covers what the tool does. It doesn't elaborate on prerequisites (like having a model open) or error handling, but these are not essential for a straightforward UI action. The description is complete enough for an agent to understand what to expect.

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 100% – the schema already documents that 'guid' is an IFC GUID with 22 characters. The description only reiterates that the component is selected by GUID, adding no new semantic detail. Baseline for full schema coverage is 3, and this does not exceed it.

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

Purpose5/5

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

The description states a specific verb ('seleciona' and 'abre') and a specific resource ('componente pelo GUID IFC' and 'janela de informacoes'). It clearly distinguishes itself from siblings like get_model_components (which retrieves data) or set_selection_basket (which changes selection) by focusing on opening an info window.

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. The description merely describes the action without mentioning conditions, prerequisites (e.g., model must be loaded), or when another tool would be more appropriate. This is a bare description with no usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools