Skip to main content
Glama

AI pre-grade

get_pregrade_info
Read-onlyIdempotent

What the SlabLineage AI-powered pre-grade is, how it works, which cards it covers, and where to start one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is fully covered without description help. The description adds that the payload is explanatory content spanning coverage/eligibility and entry points, but it does not say what form that content takes (prose, links, structured fields) or how large it is. With annotations carrying the behavioral load, a 3 is appropriate.

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?

A single compact clause with no filler, and the content list is front-loaded. It is slightly elliptical — written as a noun phrase rather than a sentence — which costs a little immediate clarity but wastes no words.

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?

For a zero-parameter, non-destructive info lookup with annotations covering safety and no output schema, the description is nearly complete. The one remaining gap is that an agent cannot predict the return format, but nothing needed to invoke the tool correctly is absent.

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 with a fully closed schema, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing or misleading.

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 resource (SlabLineage AI-powered pre-grade) and enumerates exactly what the response covers: what it is, how it works, card eligibility, and entry points. That distinguishes it from siblings like start_pregrade (which performs the action) and get_pregrade_result (which fetches an outcome), though it never names those siblings explicitly.

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?

The phrase 'where to start one' implies a routing role toward start_pregrade, and the content list implies this is a read-before-acting reference. However, there is no explicit when-to-use statement, no when-not-to-use, and no named alternative, so the agent must infer that this is a discovery/documentation call rather than an operational one.

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