vn-sketchup-mcp

Overview Schema Related Servers Score Discussions

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation4/5
Most tools target distinct operations: component creation, deletion, transformation, selection, materials, scene export, and specific joint types. The main ambiguity is eval_ruby, which can theoretically perform any operation, but its purpose as a scripting escape hatch is clear.
Naming Consistency5/5
Tool names consistently follow a verb_noun pattern, such as create_component, delete_component, transform_component, export_scene, and create_dovetail. There is no mixing of casing styles or vague verbs, making the naming predictable.
Tool Count5/5
Ten tools is a well-scoped number for a Sketchup-focused server. Each tool covers a meaningful aspect of the modeling workflow, and the count is neither too sparse nor bloated.
Completeness3/5
The tool set covers core component operations and joint creation, but lacks direct component read/list operations and joint removal or editing tools. eval_ruby can fill some gaps, but it is a generic escape hatch rather than a structured part of the domain surface.
Average 2.9/5 across 10 of 10 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 1 commit in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotions are provided, so the description carries the full burden of behavioral disclosure. It only says 'create', which implies mutation, but does not disclose default behavior (e.g., creation of a cube), coordinate/unit conventions, what happens to the selection, or side effects on the SketchUp model.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The one-sentence description is direct and front-loaded, with no wasted words. However, the extreme terseness reads as under-specification rather than efficient completeness for a tool with three undocumented parameters and no annotation support.
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?
The description covers only the core purpose. With no annotations, 0% schema coverage, undocumented parameters, and no usage or behavior context, an agent would have to guess how to invoke this tool correctly. The output schema may clarify return values, but it does not compensate for missing input semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has three parameters but zero description coverage, and the tool description names none of them. An agent cannot determine valid values for 'type', the expected format or units for 'position' and 'dimensions', or the meaning of the defaults beyond what the schema literally states.
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 and object: 'Create a new component in Sketchup'. It is distinct from delete_component, transform_component, and get_selection at the action level. However, it does not differentiate against the other create_* siblings like create_mortise_tenon or specify what kind of component, so it falls short of a 5.
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?
There is no guidance about when to use this tool versus delete_component, transform_component, or the other create_* tools. The description simply restates the action without mentioning alternatives, preconditions, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, but it only states that a joint is created. It does not say whether the source components are modified irreversibly, whether a new component is produced, how pin/tail IDs relate to the two components, or what errors or side effects may occur.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is concise and front-loaded with no filler. However, for a 10-parameter tool it is under-specified, so the brevity reflects minimal information rather than a well-structured, comprehensive description.
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?
The tool has 10 parameters, required IDs, no annotations, and no parameter explanations; the description leaves most of the invocation semantics to inference. The presence of an output schema reduces the need to describe return values, but it does not compensate for the missing usage and parameter context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description adds no explicit parameter meaning, so the burden falls entirely on property names. It offers only a weak hint that pin_id and tail_id are the two components; angle, depth, width, height, offsets, and num_tails remain semantically underspecified.
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 names a specific verb ('Create') and resource ('dovetail joint') and clarifies the scope ('between two components'), so an agent can tell it from create_component or export_scene. It does not explicitly name sibling joint tools, but the unique joint type distinguishes it from create_mortise_tenon and create_finger_joint.
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 given on when to prefer this tool over the sibling joint tools or when not to use it. The only implied context is the dovetail resource itself, and there are no exclusions, prerequisites, or alternative routing tips.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Export the current scene.' It does not state whether this writes a file, overwrites an existing file, returns a download, requires specific permissions, or has side effects. The agent is left without key behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no wasted words, which is good, but it is also under-specified. It provides only the bare action and fails to front-load any parameter or behavior information that would help an agent use the tool correctly.
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?
Although the tool is simple and has an output schema, the description omits important context such as supported formats, default behavior, output meaning, and side effects. With one parameter and no annotations, this minimal description is not enough for an agent to confidently select and invoke the tool without external assumptions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not mention the 'format' parameter at all. The schema only provides the parameter name and a default of 'skp', so the agent is not told what formats are supported or what the default implies. The parameter name is mildly self-explanatory, but the description adds no real semantic value.
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 states a clear verb and resource: 'Export the current scene.' This is unambiguous and distinguishes it from the sibling tools, which are all about component creation/deletion/transformation, materials, joints, or Ruby evaluation. However, it does not explicitly contrast with any other export-like tool, so it loses the top score.
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?
There is no guidance about when to use this tool versus an alternative, nor any mention of prerequisites or context such as whether a scene must be selected or active. The description simply states the action, leaving the agent to infer suitable invocation conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It merely says 'Create', implying a mutation, but does not explain whether components are modified irreversibly, whether material is removed, or if any side effects occur. This is minimal transparency for a creation operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with the core action front-loaded and no wasted words. It is appropriately brief, though this brevity sacrifices necessary detail that could have been included, a gap already penalized in other dimensions.
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?
For an 8-parameter tool with zero parameter documentation and no annotations, this description is far from complete. It does not explain parameter semantics, prerequisites, or behavioral effects. The existence of an output schema helps with return values, but the missing operational context remains a significant gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no parameter meaning. It does not clarify what depth, width, height, or offsets represent, in what units, or how mortise_id and tenon_id relate to the operation. The agent must guess parameter semantics from names alone.
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 action and resource: 'Create a mortise and tenon joint between two components.' This is a clear verb+resource combination that distinguishes this tool from sibling joint-creating tools like create_dovetail and create_finger_joint.
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?
There is no guidance on when to use this tool versus alternatives such as create_dovetail or create_finger_joint, nor any mention of prerequisites like whether the components must already exist or be selected. The description leaves all usage decisions to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. 'Set' implies a mutating operation, but the description does not reveal whether the material is overwritten, whether validation occurs, whether the component must exist, or what errors may arise.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no filler or redundancy. It is easily parsed and front-loads the core action, though it may be too terse to fully support the other dimensions.
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?
For a simple two-required-parameter setter with an output schema, this is minimally viable: an agent can infer id and material are needed. However, it lacks information about material value semantics, existence requirements, and side effects, which leaves meaningful gaps for a mutating tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it only restates the operation without explaining what 'id' refers to or what format/values 'material' accepts. The parameter names are self-descriptive at a basic level, but no additional meaning is provided.
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 uses a specific verb ('Set') and resource ('material for a component'), which distinguishes it from sibling tools like transform_component or delete_component. However, it doesn't specify how the material is identified (name, ID, path), leaving some ambiguity.
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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. While the operation seems self-evident, the context in which set_material should be preferred over other component tools is not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 implies mutation but does not state whether the transform fully replaces existing values, whether the component must already exist, or whether the operation is reversible. No errors, permissions, or side effects are mentioned.
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 or irrelevant content. It conveys the core purpose in eight words, and every word contributes to the meaning. This is an appropriately concise and efficiently structured definition.
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?
For a tool with four parameters (one required, three optional arrays) and no annotations, the description is underspecified. It lacks details about array formats, whether multiple transforms can be combined in one call, and the meaning of default null values. Though an output schema exists, key operational details remain missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description offers minimal compensation. It repeats the parameter names 'position', 'rotation', and 'scale' without explaining array structure, units, coordinate order, or whether rotation is Euler angles or a quaternion. This gives an agent slightly more context than the schema alone, but not enough to construct valid parameter values.
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 uses a specific verb ('Transform') and resource ('a component'), and explicitly lists the affected properties: position, rotation, or scale. This clearly identifies the tool's function and separates it from siblings like create_component or set_material. However, it does not explicitly differentiate from alternatives or state whether it modifies an existing component versus creating a new one.
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?
There is no guidance on when to use this tool versus alternatives such as create_component, delete_component, or set_material. The description only states what the tool does, leaving usage conditions entirely implicit. No exclusions, prerequisites, or alternative tool references are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It only names the primary action and does not disclose whether the operation mutates source components, how dimensions/offsets are interpreted, what happens with incompatible geometry, or whether the operation is reversible.
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?
A single front-loaded sentence that states verb, object, and operands with zero filler. The parenthetical synonym adds clarity without bloating the description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 9 parameters, zero schema descriptions, no annotations, and sibling tools for other joint types, a one-sentence purpose statement is far from sufficient. Missing parameter semantics, behavior, and usage conditions make it impossible for an agent to invoke this tool correctly with confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description adds almost no parameter meaning. The phrase 'between two components' hints that board1_id and board2_id identify the two boards, but depth, width, height, offsets, and num_fingers have no explained units, coordinate frames, or geometric constraints.
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?
States a specific verb ('Create'), a specific artifact ('finger joint (box joint)'), and the operand ('between two components'). The parenthetical disambiguates the joint type and distinguishes it from sibling joinery tools like create_dovetail and create_mortise_tenon.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the use case: select this when you need a box/finger joint between two components. However, it gives no explicit when/when-not guidance, prerequisites, or pointers to sibling joinery tools, so routing is left largely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It states that arbitrary Ruby code is evaluated, which implies potential mutability and side effects, but it does not disclose whether the code can modify the Sketchup model, whether changes are undoable, or whether there are safety implications.
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 or redundancy. Every word contributes meaning: 'Evaluate', 'arbitrary', 'Ruby code', and 'in Sketchup' all add essential context.
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?
For a tool that executes arbitrary code, the description is too sparse. It lacks critical context about side effects, execution environment, error behavior, and scope of access. The presence of an output schema helps with return values, but not with the many implicit risks of arbitrary code execution.
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 coverage is 0%, so the description must compensate. 'Arbitrary Ruby code' adds meaning to the otherwise bare 'code' parameter by defining its language and scope. However, it does not specify how the code should be structured, whether a return value is expected, or how results are returned.
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 ('Evaluate'), a clear resource ('arbitrary Ruby code'), and the execution context ('in Sketchup'). This immediately distinguishes it from the specialized sibling tools like create_component or set_material, which operate on specific Sketchup entities.
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 given about when to use this tool versus the alternatives. There is no mention of whether it should be used as a fallback when no dedicated tool exists, or whether it is intended for advanced users only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool deletes a component, but does not disclose whether deletion is irreversible, whether child or related components are also removed, what permissions are required, or what side effects occur.
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 or redundant elaboration. Every word contributes to understanding the tool's core function.
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?
For a simple one-parameter tool with an output schema, the description is minimally adequate for basic invocation. However, because it is a destructive operation and annotations are absent, the lack of information about irreversibility or cascading effects leaves a meaningful completeness gap.
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 0%, so the description must compensate. The phrase 'by ID' does add some meaning by indicating that the required id parameter identifies the component to delete, but it does not explain the ID format, where to obtain it, or any constraints on its value.
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 clearly states a specific verb (delete), the resource (component), and the identifying mechanism (by ID). It is also easily distinguished from sibling tools, none of which perform deletion.
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 given for when to use this tool versus alternatives, nor are prerequisites mentioned such as needing a valid existing component ID or whether the component must be selected. The usage context is only implied by the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description says nothing about error behavior when nothing is selected, return format, or side-effect guarantees beyond the verb. The output schema may cover return structure, but this is not disclosed in the description.
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 sentence with zero filler. It is front-loaded and appropriately sized for a zero-parameter read operation.
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 getter with no parameters and an output schema, the minimal description is almost complete. The only missing context is an explicit read-only/no-mutation guarantee, but that is reasonably inferable from the verb 'get' and the sibling tool list.
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 zero parameters, so the baseline is 4. There is nothing for the description to add about parameter meaning, and the schema already fully covers the empty parameter list.
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 uses the specific verb 'get' and names the resource 'currently selected components', clearly distinguishing this read-only tool from the sibling tools which create, delete, transform, or export. It lacks a tiny bit of scope clarification (e.g., 'in the active scene'), but the core purpose is unambiguous.
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 gives no guidance on when to use this tool or when to prefer an alternative. While the sibling list implies it is the only read tool for the selection, that is left to inference rather than stated explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![vn-sketchup-mcp MCP server](https://glama.ai/mcp/servers/andyluu98/vn-sketchup-mcp/badges/card.svg)](https://glama.ai/mcp/servers/andyluu98/vn-sketchup-mcp)

Score Badge

Copy to your README.md:

[![vn-sketchup-mcp MCP server](https://glama.ai/mcp/servers/andyluu98/vn-sketchup-mcp/badges/score.svg)](https://glama.ai/mcp/servers/andyluu98/vn-sketchup-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/andyluu98/vn-sketchup-mcp'

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