Skip to main content
Glama
Sign In
umpirix

umpirix

by caelum0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Several typed questions at once

decide

Ask multiple typed choice, score, or yes/no questions about one text in a single call and receive probability-backed answers per question.

Instructions

Ask several typed questions (choice, score, noul) about the same text in one call. Returns one typed answer per question name, each with probabilities. Use it when a decision needs more than one judgment.

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": {
      "text": "<text>",
      "questions": "<questions>"
    },
    "name": "decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to judge: a message, ticket, review, document or any other content.
modelNoOptional model id (for example system-one or auto). Defaults to the server's default model.
questionsYesMap of question name to question. At most 64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does well on the return contract — one typed answer per question name, each with probabilities — which substitutes for the absent output schema, but says nothing about side effects, cost/latency of batching many questions, or how invalid question names or per-question failures are handled.

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?

Three short sentences with zero waste: purpose and types first, then the return shape, then the usage condition. Every sentence earns its place.

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

Completeness4/5

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

For a three-parameter tool with a nested question object and no output schema, the description covers purpose, key types, and return shape adequately. The remaining gaps are the batching limits and error behavior, which matter less because the 64-question cap and per-question structure live in the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so text, questions, model, and per-question type/criteria/instructions are already documented. The description adds only that the questions are typed and share the same text, which is marginal beyond the schema; the per-type criteria semantics (e.g. score labels lowest-first) remain schema-only.

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 gives a specific verb and resource — asking several typed questions about the same text in one call — and enumerates the three question types (choice, score, noul). It distinguishes itself from single-question siblings only implicitly, via 'several ... in one call' and 'more than one judgment', without naming them.

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

Usage Guidelines4/5

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

'Use it when a decision needs more than one judgment' supplies a clear selection condition for the batched form. It stops short of explicit exclusions or of naming the single-question alternatives the agent should fall back to when only one judgment is needed.

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

Deploy Server

Other Tools