Skip to main content
Glama

jev_evaluate

Evaluate Excel, Word, PPTX, PDF, media, code, or text against multiple typed questions in parallel via the Gemini Decisions API.

Instructions

Evaluate multimodal state (Excel, Word, PPTX, PDF, media, code, text) against multiple typed questions in parallel using Gemini Decisions API.

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>",
      "questions": "<questions>"
    },
    "name": "jev_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNogemini-decision-1
stateYes
api_keyNo
questionsYes

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 supplied, so the description carries the full disclosure burden and does little. It reveals two real traits — evaluation happens in parallel and is backed by the 'Gemini Decisions API' — but says nothing about authentication expectations for api_key, cost/latency of parallel multimodal calls, failure modes, or whether evaluation mutates any external state.

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?

A single front-loaded sentence with high information density and no filler. The parenthetical format list is slightly list-heavy but every item earns its place by signaling supported input types.

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?

This is a complex tool: four parameters with nested objects, an anyOf state union, and zero schema description coverage. The description omits the shape and typing rules of the questions map and the model/api_key parameters, which are exactly the details an agent needs before a first call; only the existence of an output schema spares it from being inadequate.

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%, so the description must compensate and only partially does. It clarifies that 'state' holds multimodal content (file formats enumerated) and that 'questions' is a plural, 'typed' set, but leaves the map-shaped structure of questions, the meaning of each entry's type, the role of 'model', and the purpose of 'api_key' completely unaddressed.

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 ('Evaluate') and resource ('multimodal state') with an enumerated set of supported formats (Excel, Word, PPTX, PDF, media, code, text) and notes parallel evaluation of multiple typed questions. It does not distinguish itself from the identically-prefixed siblings jev_choice, jev_noul, jev_score, or from decision_evaluate, so an agent cannot route between them from this sentence alone.

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 prefer this tool over its siblings, no prerequisites, and no exclusions. The phrase 'against multiple typed questions in parallel' implies the batching use case, but that is inference rather than guidance.

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