Skip to main content
Glama

Score second-brain action candidates

second_brain_score_candidates
Read-only

Ranks candidates using explicit numeric evidence and a safety flag; unsafe or invalid candidates are held for review.

Instructions

Rank candidates only when safe:boolean and bounded numeric evidence fields are explicit; invalid or unsafe candidates are held.

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": {
      "candidates": "<candidates>"
    },
    "name": "second_brain_score_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidatesYes

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that unsafe or invalid candidates are held rather than causing failure or being dropped silently, but it says nothing about ranking weights, ordering guarantees, or how many results come back.

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 sentence, front-loaded with the action and immediately followed by the gating constraint, with no filler. It is efficient, though the phrase 'held' is slightly opaque without knowing the output shape.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and readOnly annotations cover safety. Still, for a scoring/ranking tool the definition never conveys the scoring model itself or error semantics per candidate, leaving an agent to infer how ranking decisions are made.

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?

With 0% schema description coverage, the description should compensate more than it does; it only explains that safe must be a boolean and that numeric evidence fields are bounded. Field names like goalFit, uncertainty, reversibility, and historicalSuccess are largely self-describing, but the description does not clarify how they are interpreted or combined.

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?

States a specific verb and resource: it ranks/scored candidates for the second-brain action pipeline, which is clearly distinct from capture, read, search, and recall siblings. The purpose is clear, but the sentence is compressed into a gating condition rather than plainly saying 'ranks candidates by scored evidence'.

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?

It gives one usage condition — rank only when safe:boolean and bounded numeric evidence fields are explicit — and says what happens otherwise (invalid or unsafe candidates are held). However, it names no alternative tool and no task-level context (e.g., when to score vs. capture or upsert a card), so guidance is implied rather than complete.

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