Skip to main content
Glama
Sign In

massprint

by com.themassprint
OverviewDiscussionsAdmin

Account behind the API key

get_account
Read-onlyIdempotent

Show the account behind your API key (Authorization: Bearer mp_live_...): its name, payment mode (invoiced for enterprise accounts) and GSTIN. massprint never messages your customers: tracking reaches you through get_order and your webhooks, and you tell your customers. Requires an API key. Enterprise accounts create and revoke keys at https://themassprint.com/business.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is lower. The description adds genuinely new context: an Authorization Bearer key is required, enterprise accounts have invoiced payment mode, and key creation/revocation happens at a specific URL — details no annotation or schema carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose well, but the sentence about never messaging customers and tracking flowing through get_order/webhooks is tangential for a read-only account lookup and dilutes focus. The auth requirement and enterprise key URL are relevant but tacked on.

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 zero-param read tool with no output schema, the description covers what an agent needs: auth requirement, the fields returned, and the enterprise key management entry point. It stops short of detailing error behavior for invalid keys, but is otherwise complete.

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?

There are zero parameters, so the baseline is 4. The description notes the API key is supplied via the Authorization header rather than as a parameter, which is a useful clarification beyond the empty 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?

States a specific verb and resource ('Show the account behind your API key') and enumerates what it returns (name, payment mode, GSTIN). This is clearly distinguishable from sibling data tools like get_order and get_catalog.

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?

Implies usage context (inspecting your own account, payment mode for enterprise billing) but never states explicit when-to-use or when-not-to-use conditions. It references get_order and webhooks for tracking, which helps route one related task, but doesn't frame this tool's role against the siblings.

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

All massprint toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources