bsdd-mcp

Search classes across dictionaries

bsdd_search_classes

Read-onlyIdempotent

Find construction classes by free-text search across all bSDD dictionaries, including IFC.

Instructions

Free-text search for classes across all bSDD dictionaries, including IFC. This is the best starting point for questions like "which class describes a wall?".

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": {
      "searchText": "<searchText>"
    },
    "name": "bsdd_search_classes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (1-1000). Defaults to 50.
`offset`	No	Zero-based offset of the first item returned. Default 0.
`searchText`	Yes	Text to search for in class names and codes.
`dictionaryUris`	No	Optional list of dictionary URIs to restrict the search to.
`relatedIfcEntities`	No	Optional filter on related IFC entities, by code (e.g. "IfcWall") or by class URI.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description doesn't need to repeat that. It adds the scope of searching all dictionaries including IFC, but does not disclose return format or pagination behavior, which is acceptable given the annotations.

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 only two sentences long, front-loaded with the core purpose and an illustrative example, with no redundant words.

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?

The tool is read-only, has well-documented schema parameters, and has no output schema. The description adequately conveys scope and when to use it, though it could optionally mention what the response contains (class objects).

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 input schema has 100% description coverage for all five parameters, so the description adds no extra parameter semantics. The example usage is helpful but does not clarify parameter details beyond the schema.

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 specifies the verb 'search' with the resource 'classes across all bSDD dictionaries, including IFC' and gives a concrete example question, which clearly distinguishes it from sibling tools like bsdd_search_text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear usage context ('best starting point') but does not explicitly list when-not-to-use or mention alternative tools for property searches, so it earns 4 rather than 5.

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

Deploy Server