Skip to main content
Glama

Start a pre-grade

start_pregrade

Creates a one-time SlabLineage upload link (valid 30 minutes) for an AI-powered pre-grade of a raw Pokémon or One Piece card. Open the link to take the two photos; the result then appears in my_pregrades. Uses the account's daily pre-grade allowance.

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": "start_pregrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesSlabLineage card id of the raw card (the number in https://slablineage.com/card/{id}).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the traits that matter: the link is one-time and expires in 30 minutes, it consumes a metered daily quota, and the outcome is asynchronously retrievable via my_pregrades. That is exactly the behavioral context an agent needs before invoking a non-idempotent, quota-consuming operation.

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 tight sentences, front-loaded with the action and resource, then the follow-up workflow and quota note. Nearly every clause earns its place; only a slight compression opportunity remains in the closing workflow sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter and no output schema, the definition covers everything an agent needs: how to call it, what the returned artifact is, its lifetime, where the result appears afterward, and the quota cost. No material gap remains for a tool of this complexity.

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?

There is a single parameter and schema description coverage is 100%, with the schema itself explaining that cardId is the numeric SlabLineage card id taken from the card URL. The description adds no further parameter meaning, which is acceptable given the schema already carries it, so the baseline 3 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 states a specific verb and resource — creates a one-time SlabLineage upload link for an AI-powered pre-grade of a raw Pokémon or One Piece card — with the relevant scope (raw cards, 30-minute validity). This clearly separates it from siblings like my_pregrades, get_pregrade_info and get_pregrade_result, which read existing pre-grades rather than initiating one.

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 gives concrete usage context: open the returned link, take two photos, and the result lands in my_pregrades, plus the constraint that it draws on the account's daily pre-grade allowance. It does not explicitly state when not to use it (e.g., already-graded slabs) or name an alternative, so it falls short of full when/when-not 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