Skip to main content
Glama

jev_noul

Evaluates a binary yes/no question using text, documents, and media inputs, returning a calibrated probability and confidence score.

Instructions

Evaluate a binary (yes/no) question against multimodal input (Excel, PDF, media, text). Returns calibrated probability (0.0 to 1.0) 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>"
    },
    "name": "jev_noul"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNogemini-decision-1
stateYes
api_keyNo
criteriaNo
question_idNonoul
instructionsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral-disclosure burden. It states the calibrated probability/confidence return, but does not disclose side effects, auth or API-key needs, model-call cost/latency, or whether evaluation is read-only or non-deterministic.

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?

The definition uses two tight sentences, front-loading the purpose before describing the return values. There is no redundant or filler wording.

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 evaluation tool with no annotations and no schema parameter descriptions, the description is too thin. It does not explain how to populate required fields like state, instructions, or criteria, though the output schema reduces the need to explain return structure.

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 does not explain any of the six parameters: state, instructions, criteria, model, api_key, or question_id. It only mentions multimodal input generically, adding no parameter-level meaning beyond the schema.

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, 'Evaluate', and resource, 'binary (yes/no) question', and names multimodal input types plus return values. It is clear what the tool does, though it does not distinguish itself from sibling evaluators such as jev_evaluate or decision_noul.

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?

The description implies use for binary yes/no questions over multimodal input, but provides no explicit when-to-use/when-not-to-use guidance. It also gives no criteria for choosing this tool over sibling decision, evaluate, or score tools.

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