Skip to main content
Glama

get_community_insight

Get aggregated print data for a model geometry. Returns local success rate, materials, settings, and failure modes, plus community insights from other prints if available.

Instructions

Get aggregated print data for a model geometry.

        Two layers, and the tool always returns whatever it can get:

        * ``insight`` — what THIS install has printed of this
          geometry: success rate, printers, materials, settings,
          failure modes.  Always available, no account needed.
        * ``community`` — the same picture across everyone who has
          printed this shape, so you can start from what already
          worked.  Community insights come with Kiln Pro
          (https://kiln3d.com/pricing); without them ``community``
          reports that it isn't available and the local layer is
          unaffected.

        Never fails because of the network or the plan: no
        connection, no account, or a plan without community
        insights all still return the local answer.

        Args:
            geometric_signature: Geometric signature to look up.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geometric_signatureYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it always returns the local answer, community insights depend on subscription, and the tool never fails due to missing network, account, or plan. This level of detail gives the agent complete understanding of the tool's behavior in various scenarios.

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 well-structured with a clear first sentence stating the purpose, followed by bullet-like explanations of the two layers and error handling. It is slightly verbose but every sentence adds value, and the key information is front-loaded.

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

Completeness5/5

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

Given the simple input schema with one parameter and no output schema, the description comprehensively covers behavior, edge cases (no connection, no account, no community), and prerequisite (Kiln Pro). It provides all necessary context for the agent to use the tool correctly.

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 description adds meaning to the single parameter 'geometric_signature' beyond the schema, explaining it as the 'Geometric signature to look up.' Since schema coverage is 0%, this provides essential context that the agent needs.

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 the tool gets aggregated print data for a model geometry. It specifies two distinct layers (insight and community) and uses a specific verb+resource combination that distinguishes it from sibling tools like troubleshoot_print_issue or check_printer_material_compatibility.

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 explains when to use the tool: anytime aggregated print data is needed for a specific geometry. It notes that the local layer is always available with no account, while community insights require Kiln Pro. It also states the tool never fails due to network or plan, providing clear context for its usage.

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/codeofaxel/kiln'

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