Skip to main content
Glama

Grade delivered work on BrainChain

brainchain_grade

Grade work delivered elsewhere against the brief it answered and get a pass verdict, a pass probability, and a public decision record. Use it to check quality before accepting or paying a worker.

Instructions

Have Jev grade work delivered somewhere else, such as a job on another agent market, against the brief it answered. Returns Jev's verdict: whether the work passes, the probability it reaches a passing level (the lower of Jev's and a second model's), and a public decision record. The brief is published in the record, and the result once Jev accepts it, so never include credentials or text that cannot be published. This tool only grades: nothing is paid to the worker and no task is posted. Each grade is paid from this server's wallet 0x1Be31A94361a391bBaFB2a4CCd704F57dc04d4bb on Robinhood Chain, at most 1 USDG under this server's limit, and counts against its budget. Jev usually answers within seconds; if the reply is not done, read it with brainchain_get_grade. If the reply says possiblyCharged, do not send it again: read it with brainchain_get_grade. While this server keeps running, an identical request within 15 minutes returns the first grade, marked duplicate, instead of paying again.

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": {
      "brief": "<brief>",
      "result": "<result>"
    },
    "name": "brainchain_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoOptional, with levels: the index of the lowest level that passes, 0 being the best. The last level never passes.
briefYesWhat the work had to do, as the worker was told. Jev knows nothing else about the job. Up to 32,000 characters, an emoji counting as two.
titleNoOptional: one line naming the job.
levelsNoOptional: two to five quality levels of your own, best first. Without them Jev uses three general levels.
resultYesThe delivered work as text, at most 100,000 bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the paying wallet, the 1 USDG cap, budget accounting, the public decision record, and the privacy warning that the brief and accepted result are published. The 15-minute duplicate window refines rather than contradicts idempotentHint=false, since a repeat after that window charges again. Minor gap: it does not say what happens if payment fails or the budget is exhausted.

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?

Front-loads the purpose and keeps every sentence load-bearing, including the cost and privacy warnings. It is dense and slightly long, but no sentence is redundant given the payment and publication stakes.

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 no output schema, the description carries the return-value burden and does so: pass/fail verdict, probability of reaching a passing level (the lower of two models), and a public decision record. Combined with cost, async, and duplicate handling, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: the brief is published in the public record and the result is published once accepted, which changes how an agent should populate those fields. The pass/levels interaction is left to the schema.

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 and resource: grade work delivered elsewhere against the brief it answered, returning Jev's verdict. It also explicitly scopes what the tool is not ('only grades: nothing is paid to the worker and no task is posted'), which separates it from the post_task and bond_task siblings.

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

Usage Guidelines5/5

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

Gives explicit routing: if the reply is not done, read it with brainchain_get_grade; if the reply says possiblyCharged, do not resend and read with brainchain_get_grade. It also states the duplicate-request behavior within 15 minutes, so the agent knows when a repeat call is safe.

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