Skip to main content
Glama

Pre-grade result

get_pregrade_result
Read-onlyIdempotent

One of your pre-grades: the PSA and TAG grade ranges, whether it is guarantee eligible and why not, the report and upgrade deadlines, the claim status, and the upgrade link while the upgrade window is open.

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": {
      "estimateId": "<estimateId>"
    },
    "name": "get_pregrade_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
estimateIdYesYour pre-grade id (from my_pregrades).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context beyond them: it discloses that guarantee eligibility comes with a reason, and that the upgrade link is only present 'while the upgrade window is open', which explains a conditionally absent field. It stops short of noting error behavior for an invalid or foreign estimateId.

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?

One compact sentence with the most important output (grade ranges, eligibility) first and secondary fields after. It is a fragment rather than a verb-led statement, but every clause corresponds to a real returned field, so nothing is wasted.

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 needs to convey the return shape, and it does so field by field for a one-parameter read tool. What remains missing is a clear boundary against the adjacent pre-grade detail tool, which matters more here than additional return detail.

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 coverage is 100% and the single parameter is documented as 'Your pre-grade id (from my_pregrades)', so the schema carries the load. The description adds no further meaning about the identifier's scope (ownership, validity) beyond what is already structured, so baseline 3 applies.

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 enumerates the concrete payload of the tool (PSA/TAG grade ranges, guarantee eligibility and reason, report/upgrade deadlines, claim status, upgrade link), which makes it clearly a single-pre-grade result lookup. It does not, however, distinguish itself from the sibling get_pregrade_info, so the agent must guess which detail tool to call.

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?

Usage is only implied: the tool reads one existing pre-grade's outcome, and the schema note points at my_pregrades as the id source. There is no explicit statement of when to use this versus get_pregrade_info or my_pregrades, and no precondition such as 'only after grading completes' or what happens while the grade is still pending.

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