Skip to main content
Glama

Should I grade this?

grade_math
Read-onlyIdempotent

The SlabLineage grading calculator for a raw Pokémon or One Piece card: net result at PSA and TAG 9 and 10 after the grading fee, the recommended tier and a verdict. Uses the website's default selling fees (13.25% plus $0.40 per order, no shipping) unless you pass your own.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cardId": "<cardId>"
    },
    "name": "grade_math"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesSlabLineage card id (the number in https://slablineage.com/card/{id}).
feePctNoSelling fee percent (default 13.25).
psaTierNoPSA service tier name; default is the cheapest tier that covers the 10 price.
tagTierNoTAG service tier name; default is the cheapest tier that covers the 10 price.
orderFeeNoPer-order fee in USD (default 0.40).
shippingNoShipping cost in USD (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful substance beyond that: the calculations assume the website's default selling fees (13.25% plus $0.40 per order, no shipping) unless overridden, which tells the agent what assumptions underlie the verdict. It does not disclose price freshness or whether the underlying comps are live, a remaining gap.

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

Conciseness4/5

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

Two sentences with the identity and output shape front-loaded, then the fee-default caveat. Dense but no filler; a slight readability cost comes from packing outputs, tier logic and fee assumptions into one long clause.

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 six parameters, one required, full schema coverage and no output schema, the description compensates reasonably by naming the returned fields (net result per grader/tier, recommended tier, verdict). What is missing is the provenance/freshness of the prices behind those numbers, which matters for a financial-decision tool.

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 every parameter is already documented, and the description mostly restates the fee defaults (feePct, orderFee, shipping). It does add coherence by framing the fee trio as a single 'website default' model, but adds nothing about psaTier/tagTier selection or cardId beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb-and-resource ('grading calculator for a raw Pokémon or One Piece card') and even enumerates what it returns: net result at PSA and TAG 9/10, recommended tier, verdict. An agent can tell this is an evaluate-before-submitting tool rather than a lookup. It never names a sibling such as get_pregrade_info or get_pregrade_result to draw the boundary explicitly.

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

Usage Guidelines2/5

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

The title 'Should I grade this?' implies the decision context, but the description never says when to use this versus get_pregrade_info/get_pregrade_result or the deal tools, nor any when-not conditions. The only guidance-like sentence concerns overriding fee defaults, which is parameter behavior, not tool selection.

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