Skip to main content
Glama

My Printlooper account

get_my_account
Read-onlyIdempotent

Who is connected: first name, account type (designer, seller or print shop), which permissions were granted, and where to manage the account. Call this first to know which tools apply. Needs a connected Printlooper account.

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_my_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the bar is lower. The description adds non-obvious context the annotations cannot carry: the output includes granted permissions (which governs what other tools are usable) and an authentication precondition requiring a connected account.

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?

Three short sentences, each doing distinct work: contents, calling order, precondition. The most important instruction ('Call this first') is front-loaded immediately after the return-value summary, with no filler.

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?

With no output schema, the description correctly enumerates what comes back, so an agent knows the shape of the response. It does not say what happens when no account is connected (error vs. empty result), a minor gap for an otherwise simple, well-specified read tool.

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?

This tool has zero parameters, so the baseline of 4 applies. No parameter detail is needed or missing.

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 names the specific resource and the fields returned: first name, account type with its three enumerated values (designer, seller, print shop), granted permissions, and account-management location. It is clearly distinguishable from siblings like get_my_earnings or get_my_shop, though the verb is implied ('Who is connected') rather than stated as a direct action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first to know which tools apply' gives an explicit ordering rule that selects this tool over all siblings. The precondition 'Needs a connected Printlooper account' tells the agent when the tool is available at all, leaving nothing to inference.

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.

Resources