Skip to main content
Glama

jev_score

Score multimodal inputs against an ordered rubric of two or more descriptive levels, returning a weighted float score and confidence.

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": "jev_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.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only that the tool returns a weighted float and confidence. It says nothing about authentication via api_key, model selection behavior, rate limits, determinism, or what happens when criteria/instructions are malformed.

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, front-loaded with the purpose and followed by the return contract. There is no filler or repetition.

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?

The output schema covers return values, so the description need not explain them. But for a six-parameter tool with zero schema descriptions and no annotations, the definition is far too thin: it leaves parameter usage, input formats, and behavioral constraints undocumented.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning for any of the six parameters. Terms like 'rubric' hint at the criteria parameter, but state, instructions, question_id, model, and api_key are entirely unexplained in both schema and description.

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 states a specific verb and resource: 'Rate multimodal input along an ordered rubric.' It also says what is returned, a weighted float score and confidence. It does not distinguish this tool from siblings such as jev_evaluate or decision_score, so it stops short of a 5.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The sibling set contains several similarly named scoring/evaluation tools, making the absence of routing guidance a real gap.

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