hip_get_service_info
What Have It Printed does, what it costs, what file types and sizes are accepted, and how mailing works. Public; no account needed.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Have It Printed
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It at least reveals that calling the tool requires no account and implies a read-only informational operation. It does not describe response format, caching, or rate limits, but for a parameterless public info lookup that is a relatively minor gap.
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 two short sentences with no filler: the first front-loads the content topics, and the second adds the access constraint. Both sentences earn their place, and the structure is easy for an agent to parse quickly.
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 parameterless public info endpoint, the description covers the returned information scope and the access model. Since there is no output schema or nested objects, the description is nearly complete, though a brief note about using this for general service info rather than personalized quotes would fully close the loop.
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 and the schema already fully captures this with an empty properties object. There is no parameter meaning for the description to add, so the baseline 4 for a zero-parameter tool applies.
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 specifies the resource (Have It Printed service information) and enumerates its content: what the service does, costs, accepted file types/sizes, and mailing behavior. Though the description lacks an explicit verb, the tool name 'get_service_info' supplies the action, and the informational topic clearly distinguishes it from transactional siblings like payments, checkout, and job creation.
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 states that the tool is public and requires no account, which is useful guidance for when this endpoint is appropriate. However, it does not explicitly contrast this with siblings such as hip_quote, leaving the boundary between general cost information and job-specific quotes implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation4/5
Most tools are clearly distinct by resource and action, such as create_job vs update_job or complete_payment vs create_checkout. However, hip_quote and hip_prepare_payment both return pricing information and could be confused at first glance; the descriptions do clarify their different purposes, but an explicit warning is needed to keep them apart.
Naming Consistency5/5
All tools follow the same hip_ prefix with verb_noun snake_case naming, such as hip_create_job, hip_get_order, and hip_complete_payment. This makes the toolset predictable and easy to navigate.
Tool Count5/5
Ten tools is well-scoped for a print-and-mail service. Each tool covers a necessary part of the workflow—job creation, document upload, quoting, payment, and order tracking—without unnecessary duplication or bloat.
Completeness4/5
The core lifecycle is well covered: create and update a job, upload documents, quote, pay via autonomous or checkout flows, check payment status, and retrieve order tracking. Minor gaps exist, such as no explicit cancel/delete job or a pre-payment job status retrieval tool, but agents can likely work around these.