Skip to main content
Glama

Compare my prices

get_pricing_benchmarks
Read-onlyIdempotent

How your price per gram and minimum job compare with other approved Printlooper shops, per material (low quartile, median, high quartile). Shown only where enough shops offer the material to keep each shop anonymous. 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_pricing_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds two things beyond that: an authentication prerequisite and a privacy gating rule ('shown only where enough shops offer the material to keep each shop anonymous'), which tells the agent results may be absent for thin materials. It doesn't say what a partial/empty result looks like, keeping it below a 5.

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 comparison and the returned statistics, followed by the anonymity caveat and the account requirement. Every clause carries information; nothing is redundant with the title or annotations.

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 carries the burden of explaining returns and does so at the level of metrics and grouping, plus the anonymity gate and auth requirement. The main residual gap is what the agent should expect when no comparison is available (empty vs. omitted entries), which matters for a gated 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The mention of 'per material' is about output grouping rather than input, which is consistent with 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?

The description names a specific comparison task ('how your price per gram and minimum job compare with other approved Printlooper shops'), the unit of analysis (per material), and the exact statistics returned (low quartile, median, high quartile). An agent can immediately distinguish this read-only benchmarking tool from siblings like set_material_prices or get_my_earnings.

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?

It states the condition for use (you want to see how your own prices compare with peers) and a prerequisite ('needs a connected Printlooper account'), which is actionable context. It stops short of naming alternatives or explicitly excluding cases, so it sits at clear-context-but-no-exclusions rather than full routing guidance.

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