Skip to main content
Glama

get_categories

Retrieve all category information from a Revit model to access and organize building element classifications for analysis and documentation.

Instructions

获取 Revit 模型中的所有类别

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:117-123 (registration)
    Registration of the 'get_categories' tool in the ListToolsRequestSchema handler, including its schema (empty input).
      name: "get_categories",
      description: "获取 Revit 模型中的所有类别",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }, {
  • Input schema for get_categories tool: empty object.
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Primary handler for 'get_categories' tool: calls socket client and handles errors.
    async getCategories(): Promise<any[]> {
      try {
        return await this.client.getCategories();
      } catch (error) {
        console.error('[RevitService] 获取类别失败:', error);
        throw error;
      }
    }
  • Helper function that sends the actual 'get_categories' command to the Revit socket server.
    public async getCategories(): Promise<any[]> {
      const response = await this.sendRequest<any[]>('get_categories', {});
      return response;
    }
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 the action but does not reveal any behavioral traits, such as whether this is a read-only operation, if it requires specific permissions, or what the return format might be. This is a significant gap for a tool with zero annotation coverage.

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 directly states the tool's purpose without any waste. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the complexity of interacting with a Revit model, the description is incomplete. It lacks details on behavioral traits, output format, and how the model context is provided, especially with no annotations and no output schema. This makes it inadequate for an agent to fully understand the tool's operation.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it implies the tool operates on a Revit model context without specifying how that context is established. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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

Purpose4/5

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

The description clearly states the verb '获取' (get) and resource 'Revit 模型中的所有类别' (all categories in a Revit model), making the purpose specific and understandable. However, it does not explicitly distinguish this tool from sibling tools like 'get_families' or 'get_elements', which might also retrieve related model data, so it misses full 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 does not mention context, prerequisites, or exclusions, such as whether it requires an open model or how it differs from sibling tools like 'get_families'. This leaves the agent with minimal usage direction.

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/PiggyAndrew/revit_mcp'

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