Skip to main content
Glama

Polemia question of the day

daily_question
Read-onlyIdempotent

Today's Polemia question: one opinion question a day, answered anonymously by people all over the world. Free. Use it when the user wants a question of the day, a conversation starter, or to see what the world thinks. Returns the question, its answer options and answer_url, where the user votes and then sees everyone's results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "daily_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoShow the question in this language when a translation exists (BCP-47). Default English.

Output Schema

NameRequiredDescriptionDefault
dateYes
optionsYes
languageYes
questionYes
answer_urlYes
how_it_worksYes
past_results_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / how_it_works
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / instructions
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "date",
      -  "question",
      -  "options",
      -  "language",
      -  "answer_url",
      -  "past_results_url",
      -  "instructions"
      -]New value: +[
      +  "date",
      +  "question",
      +  "options",
      +  "language",
      +  "answer_url",
      +  "past_results_url",
      +  "how_it_works"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description adds real context beyond that — answers are anonymous, the resource is free, and the user must follow answer_url to vote and see aggregate results. It does not say how 'daily' rolls over (timezone/reset) or whether results are cached, which is a minor gap.

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?

It is front-loaded with the core fact (one opinion question a day) and then covers usage and return shape in two further sentences. Slightly padded with promotional fragments ('Free.', 'answered anonymously by people all over the world'), but nothing is genuinely wasteful.

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

Completeness5/5

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

For a one-optional-parameter read tool with annotations, an output schema and full schema coverage, the description supplies everything needed: what it returns, what answer_url is for, and when to reach for it. Nothing essential is missing.

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?

There is a single optional parameter (language) and schema description coverage is 100%, including the BCP-47 format and the default. The description itself adds nothing about the parameter, so the schema does the heavy lifting — the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource — the single daily opinion question from Polemia — plus what a caller gets back (question, answer options, answer_url). It is clearly distinct from the sibling tools create_quiz and find_quizzes, which are about authoring and searching quizzes rather than fetching today's question.

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 gives explicit trigger conditions: 'Use it when the user wants a question of the day, a conversation starter, or to see what the world thinks.' That is a clear positive usage context, though it names no alternatives or when-not conditions (e.g. searching past questions via find_quizzes).

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