Skip to main content
Glama

Poem of the day

poem_of_the_day
Read-onlyIdempotent

Today's poem of the day in a language (English by default): title, poet, opening lines (a poem of 1 to 3 lines whole) and link.

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": "poem_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the poems, an ISO 639-1 code: en, ru, be, de, fr, es, it, pl, nl, sv, da, nb or uk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavior, so the safety profile is covered. The description adds value beyond that by spelling out the return payload (title, poet, opening lines, link) and noting that very short poems are returned whole — useful given there is no output schema.

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 no wasted preamble; the fallback language and the return fields are packed in efficiently. The parenthetical '(a poem of 1 to 3 lines whole)' is slightly awkward but earns its place by clarifying truncation behavior.

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 one-optional-parameter read tool with no output schema, the description covers the return shape, the language default, and the truncation rule. Minor omissions (e.g., whether the poem changes daily, caching) are low-stakes for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and the enum is fully documented, so the baseline is 3. The description adds the default ('English by default'), which the schema does not encode since the parameter is optional with no default field — a genuine semantic addition.

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 names a specific resource ('today's poem of the day') and enumerates the returned fields (title, poet, opening lines, link), which is enough to distinguish it from siblings like get_poem or find_poems. It lacks an explicit verb and does not state how it differs from the daily/random poem siblings, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the name and the phrase 'today's poem of the day' — an agent can infer this is for the current daily poem, and 'English by default' signals the parameter is optional. There is no explicit when-to-use or when-to-prefer-get_poem/find_poems guidance.

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