Skip to main content
Glama

kernelcad

by com.kernelcad

Query Geometry

query
Read-only

Use this when you need to resolve or inspect topology against a script's lowered geometry. Selected by mode (default 'evaluate'):

  • 'evaluate' — inspect a Query (@kc[...] ref, @kcq[...] DSL, or { ast }); returns matched entities. Pass expect:'unique' to assert exactly-one.

  • 'resolve' — resolve a single @kc[...] / @kcq[...] ref to one entity ({ ref }).

  • 'lineage' — walk the HistoryMap for a named face ref ({ feature_id, ref }). All params except mode are forwarded verbatim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNomode:'resolve'|'lineage' — topology ref string.
codeNoInline kernelCAD script source.
fileNoPath to a .kcad.ts script file.
modeNoResolution mode (default 'evaluate').
queryNomode:'evaluate' — Query input: @kc[...] / @kcq[...] string or { ast } object.
expectNomode:'evaluate' — 'unique' asserts exactly-one.
feature_idNoOptional FeatureId; defaults to the last lowered shape (use "auto" for lineage).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
refNomode:'resolve' — the resolved ref string.
chainNomode:'lineage' — HistoryMap walk.
errorNo
queryNomode:'evaluate' — the resolved Query ({ ast }).
entityNomode:'resolve' — the single matched entity.
entitiesNomode:'evaluate' — matched entities.
warningsNo
errorCodeNo
candidatesNomode:'resolve' — near-miss candidates (failure).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds behavioral context: explains what each mode returns, parameter forwarding, and the 'expect' constraint. It does not cover potential side effects or limitations, but the annotations cover the safety profile.

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 concise, using a bullet list for modes and clear language. Every sentence adds value, with no filler or repetition.

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?

Given the complexity of three modes and seven parameters, the description is largely complete. It explains purpose, mode selection, and parameter roles. Since an output schema exists, not detailing return values is acceptable. Minor gaps: no mention of error conditions or response structure.

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?

Schema coverage is 100%, and the description adds mode-specific parameter guidance (e.g., which params apply to each mode). This clarifies usage beyond the schema's parameter descriptions without redundancy.

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 it resolves or inspects topology against a lowered geometry, with three distinct modes (evaluate, resolve, lineage) each having a specific purpose. This differentiates it from sibling tools like 'inspect' or 'evaluate_script' by focusing on querying via ref, DSL, or AST.

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?

The description opens with 'Use this when you need to resolve or inspect topology against a script's lowered geometry' and breaks down when each mode is appropriate. However, it does not explicitly state when not to use this tool or name alternative tools from the sibling list.

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

All kernelcad toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are mostly distinct, with clear descriptions for each. However, there is some potential overlap between inspection tools like 'inspect' and 'mesh_summary', and between rendering tools 'render_preview' and 'get_latest_render', which could cause minor confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, making it predictable for an agent to infer functionality.

Tool Count2/5

44 tools is significantly higher than the typical well-scoped range of 3-15. While the domain is complex, the count feels excessive and could overwhelm an agent.

Completeness4/5

The tool set covers an extensive range of CAD operations including creation, inspection, rendering, export, and verification. Minor gaps exist, such as direct sketch editing tools, but overall it is comprehensive.

Resources