Skip to main content
Glama

ai_modeling_print_shop

Read-only

Retrieves JuJuBit print-shop information for a project without publishing it or creating an order; private projects require a separate explicit visibility action.

Instructions

Read JuJuBit print-shop information for a project. Private projects require a separate explicit native visibility action; never publishes a project or creates an order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "ai_modeling_print_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is supplied. The description adds two genuinely useful behavioral facts beyond that: it never publishes or creates orders, and private projects need a separate explicit visibility action, warning that results may be incomplete for private projects. It still says nothing about auth requirements, what the external JuJuBit service returns on failure, or rate limits, leaving real gaps for an open-world tool.

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?

Two compact sentences with the purpose front-loaded and the constraints trailing. Nothing is padding, though 'separate explicit native visibility action' is dense internal jargon that an agent may not be able to act on.

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 one-parameter read-only tool with no output schema, the definition covers the safety and side-effect boundary well. It does not indicate what print-shop data is actually returned, such as materials, pricing, availability, or vendor options, which is the main remaining gap for an agent deciding whether to call it.

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?

There is one required parameter and schema description coverage is 0%, so the description must carry the meaning. 'For a project' only weakly signals that project_id scopes the lookup; it does not explain the accepted ID form or what happens when the ID refers to a private project, which is exactly where the visibility caveat matters.

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 specific verb and resource: 'Read JuJuBit print-shop information for a project.' An agent can tell it is a read-only inspection of print-shop data. However, it gives no hint of what distinguishes it from siblings such as ai_modeling_print_plan, ai_modeling_print_targets, or ai_modeling_print_open, and 'print-shop information' remains an undifferentiated catch-all.

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?

There is a negative boundary ('never publishes a project or creates an order'), which implicitly tells the agent this is not the tool for ordering or publishing. But there is no positive when-to-use statement and no named alternative for the planning, target, or open operations that the sibling names suggest exist.

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

Deploy Server

Other Tools