Skip to main content
Glama

printing-labs

by com.printinglabs

request-quote

Submit a corporate quote request to the Printing Labs sales team on the user's behalf. Creates a real lead: the team receives it instantly (CRM + email + WhatsApp) and the requester gets a confirmation email. Only submit with the user's explicit consent and their real contact details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRequester's full name
emailYesRequester's email address (receives the confirmation)
phoneNoPhone / WhatsApp number with country code
companyNoCompany name
messageYesWhat they need — products, quantities, timelines, customization
quantityNoApproximate unit quantity
productSlugsNoProduct slugs from search-products the quote is about

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and excels: it discloses real-world consequences (creates a real lead, team receives via CRM+email+WhatsApp, requester gets confirmation) and emphasizes consent. This goes beyond typical mutation descriptions.

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?

Two sentences, front-loaded with the action, followed by consequences and a constraint. Every sentence earns its place with zero waste.

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 7-param mutation tool without output schema, the description covers purpose, consequences, and consent requirement. Slightly lacks guidance on when to prefer this over related tools, but overall complete enough for correct invocation.

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 100%, so baseline is 3. The description reinforces that contact details must be real and that email receives confirmation, but doesn't add new parameter-specific meaning beyond the schema.

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 verb and resource: 'Submit a corporate quote request to the Printing Labs sales team.' It also distinguishes from siblings by noting it creates a real lead, unlike search-products or get-product-details.

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 provides clear context: acts on the user's behalf, requires explicit consent and real contact details. It lacks explicit mention of alternatives (e.g., calculate-bulk-price), but the conditional consent constraint gives practical usage guidance.

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

All printing-labs 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

A4/5.0
Disambiguation5/5

Each tool targets a distinct action or resource: product discovery vs pricing vs orders vs meetings vs support. While get-company-info, get-site-info, and get-guide all provide reference material, their scopes are clearly separated (verified facts vs FAQ/how-it-works vs published articles). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: book-, cancel-, reschedule-, get-, search-, list-, request-, track-, reorder-, create-. Even exceptions like my-orders and my-invoices fit a possessive pattern that is predictable. No mixed conventions or vague verbs.

Tool Count4/5

24 tools is on the high end but appropriate for the breadth of this server's scope: product catalog, pricing, meetings, orders, invoices, support, guides, company info, and SEO. Each tool fills a specific niche, and none feel redundant. It is slightly heavy but not overwhelming for the domain.

Completeness4/5

The tool surface covers the core workflows well: product search/details/pricing, meeting booking/cancel/reschedule, order viewing/tracking/reordering, quotes, complaints, callbacks, invoices, guides, and company information. A minor gap is the absence of a direct 'place new order' tool, but request-quote and reorder handle the necessary paths, and other interactions (e.g., complains) have clear entry points.

Resources