Skip to main content
Glama

get_levels

Retrieve all floor levels from a Revit model to access building elevation data and structural information for design analysis and documentation.

Instructions

获取 Revit 模型中的所有楼层

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:160-167 (registration)
    Registration of the "get_levels" MCP tool in ListToolsRequestSchema, defining its name, description, and empty input schema.
    {
      name: "get_levels",
      description: "获取 Revit 模型中的所有楼层",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }, {
  • Input schema for the get_levels tool (no parameters required).
    inputSchema: {
      type: "object",
      properties: {}
    }
  • The handler function in RevitService that executes the get_levels tool logic by delegating to RevitSocketClient.getLevels().
    async getLevels(): Promise<any[]> {
      try {
        return await this.client.getLevels();
      } catch (error) {
        console.error('[RevitService] 获取楼层失败,使用模拟数据:', error);
        throw error; // 不使用模拟数据,直接抛出错误
      }
    }
  • Supporting utility in RevitSocketClient that sends the 'get_levels' command to the Revit plugin via socket and returns the levels.
    public async getLevels(sortByElevation: boolean = true): Promise<any[]> {
      const response = await this.sendRequest<any[]>('get_levels', {  });
      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 tool retrieves data ('获取'), implying a read-only operation, but doesn't specify permissions, rate limits, output format, or potential side effects. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence: '获取 Revit 模型中的所有楼层'. It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool. Every word earns its place, making it highly concise and well-structured.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks behavioral details like output format or usage context. For a basic retrieval tool, this is adequate but leaves clear gaps, especially with no annotations to compensate.

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 there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as the description doesn't mislead or omit necessary param info.

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 tool's purpose: '获取 Revit 模型中的所有楼层' (Get all floors in the Revit model). It specifies the verb '获取' (get) and resource '楼层' (floors) with scope 'Revit 模型中的所有' (all in the Revit model). However, it doesn't explicitly differentiate from sibling tools like 'get_elements' or 'get_categories', which might also retrieve model data.

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 doesn't mention prerequisites, context, or exclusions, and doesn't reference sibling tools like 'get_elements' or 'get_categories' that might overlap in functionality. This leaves the agent with minimal usage context.

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