Skip to main content
Glama

decision_noul

Evaluates binary yes/no questions against multimodal Excel, PDF, media, and text inputs to return 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": "decision_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
Behavior3/5

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

With no annotations provided, the description carries the full burden; it does disclose the output semantics (calibrated probability 0.0 to 1.0 plus confidence) and the multimodal input scope, which is useful behavior beyond structure. However it says nothing about authentication (an api_key parameter exists), cost/latency, what 'calibrated' implies, or how the tool handles non-binary or ambiguous questions.

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?

Two compact sentences, front-loaded with the core action followed by the return contract; no filler or redundancy. It is arguably too terse for a 6-parameter tool, but every sentence present earns its place.

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?

An output schema exists, so the return-value sentence is largely redundant and the description need not expand there. The real gaps are elsewhere: no usage routing among five similarly named siblings and no explanation of four documented-by-name-only parameters, leaving an agent unable to call this correctly without guessing.

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 6 parameters, so the description must compensate, but it explains none of them. It does not clarify what 'state', 'instructions', 'criteria', 'model', 'api_key', or 'question_id' mean, nor how state/instructions may be a string, object, or array despite that being a major ambiguity.

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: 'Evaluate a binary (yes/no) question against multimodal input', plus the accepted input types (Excel, PDF, media, text). It is distinguishable from siblings like decision_score or jev_evaluate only by the 'binary yes/no' framing, since no sibling is named explicitly.

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 versus decision_choice, decision_evaluate, or decision_score, and no preconditions, exclusions, or example scenarios. The agent must infer usage purely from the phrase 'binary (yes/no) question'.

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