Skip to main content
Glama

decision_score

Scores multimodal inputs against an ordered rubric with at least two descriptive levels, returning a weighted float score and confidence for consistent comparisons.

Instructions

Rate multimodal input along an ordered rubric of at least two descriptive levels. Returns a weighted float score and confidence.

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": {
      "state": "<state>",
      "instructions": "<instructions>",
      "criteria": "<criteria>"
    },
    "name": "decision_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNogemini-decision-1
stateYes
api_keyNo
criteriaYes
question_idNoscore
instructionsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and mostly does not meet it: it says the result is a weighted float plus confidence but never states required credentials despite an api_key parameter, whether the model is selectable or what happens with fewer than two levels. The mention of a weighted score is the one genuinely useful behavioral detail.

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 tight sentences with the action first and the return shape second; nothing is redundant or padded.

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

Completeness2/5

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

For a six-parameter tool with no annotations and zero schema descriptions, the definition is too thin. The output schema excuses it from explaining return values, but it should still clarify the roles of state, instructions, and criteria, and whether an API key is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description is the only source of meaning and it explains almost none of them. 'Multimodal input' hints at state and the 'ordered rubric' hints at criteria, but instructions, model, api_key, and question_id are left entirely opaque, leaving an agent to guess at how to shape the call.

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 concrete verb and resource: rate multimodal input against an ordered rubric, returning a weighted float score and confidence. That is specific enough to act on, but nothing distinguishes it from the equally named sibling jev_score, or explains how rating on a rubric differs from decision_evaluate or decision_choice.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool instead of the sibling scoring, choice, evaluate, or noul variants. The only implicit constraint is 'at least two descriptive levels,' which is a rubric-shape rule, not usage guidance.

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