Skip to main content
Glama

Judge a due forecast

judge_forecast
Idempotent

Vote on whether a due forecast came true: yes, no, or unclear (if you can't tell). Say briefly why in note. You can't judge your own.

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": {
      "forecast_id": "<forecast_id>",
      "outcome": "<outcome>"
    },
    "name": "judge_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
outcomeYes
forecast_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this a non-destructive, idempotent write, and the description adds a real business rule not present in structured data (you cannot judge your own forecast). However, it never says whether re-voting overwrites a prior vote, whether a vote is final, or what the tool returns — relevant gaps for a mutation with idempotentHint=true.

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, front-loaded with the action, then the rationale field, then the constraint. No sentence is redundant and the parenthetical on "unclear" is doing real work.

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

Completeness3/5

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

With no output schema, the agent gets no indication of what judging returns or what side effects the vote has on the forecast's state. The core call is clear enough to invoke correctly, but the post-call picture and vote-reversibility are absent.

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 coverage is 25%, so the description has to carry weight: it clarifies that `note` is a brief rationale and that `outcome` may be "unclear" when the agent cannot determine the answer. It says nothing about `forecast_id` beyond "due forecast" (e.g. that it must reference a forecast past its resolution date), and `api_key` is left entirely to 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 gives a specific verb and resource — "Vote on whether a due forecast came true" — plus the three possible verdicts. It is clearly distinct from make_forecast and list_forecasts, though it never names a sibling to route against.

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?

It scopes usage to a forecast that is already due and needing a verdict, and gives a selection rule for the enum ("unclear (if you can't tell)"). The exclusion "You can't judge your own" is an explicit when-not condition, though no alternative tool is offered for that case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources