Skip to main content
Glama

Read a BrainChain grade

brainchain_get_grade
Read-only

Retrieves a BrainChain grade record by ID, returning the verdict, pass probability, per-level probabilities, and decision details; poll again after retryAfterSeconds until done is true.

Instructions

Read a grade from brainchain_grade: Jev's verdict, the pass probability, each level's probability and the decision record. Free, no key. Call again after retryAfterSeconds until done is true.

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": {
      "grade": "<grade>"
    },
    "name": "brainchain_get_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
gradeYesGrade id returned by brainchain_grade.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real value on top by disclosing cost (free), auth (no key), and the asynchronous completion contract (poll on retryAfterSeconds until done). It does not cover failure modes such as an unknown or expired grade id, which keeps it short of 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 short sentences with zero filler: the payload is front-loaded, then the polling instruction follows. Every clause (free, no key, retryAfterSeconds, done) carries actionable information.

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?

There is no output schema, but the description compensates by naming the return fields (verdict, pass probability, level probabilities, decision record) and explaining the done/retryAfterSeconds completion signal. Combined with annotations covering the safety profile, an agent has everything needed to call and poll it correctly.

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%, and the schema already constrains the single parameter to a 32-byte hex grade id via a regex. The description adds no format or syntax detail beyond echoing that the id comes from brainchain_grade, so the baseline of 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?

States a specific verb ('Read') and resource ('a grade from brainchain_grade') and then enumerates the payload: Jev's verdict, pass probability, per-level probability, and the decision record. This implicitly separates it from the sibling brainchain_grade that produces the grade id, so an agent can route between the two without opening either schema.

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?

Gives concrete operational guidance: it is free, needs no key, and should be re-called after retryAfterSeconds until done is true. That tells the agent exactly how to drive the polling loop, but there is no explicit statement of when not to use it or which sibling to pick for other grade-related needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.