Margaret's poems

A poem to give someone

random_poem

Read-only

One good poem at random, one that stands alone without context, for handing to someone rather than looking for one. Narrow it by theme, mood, form or collection.

Input Schema

Name	Required	Description
`form`	No	rhymed-metred, rhymed-loose, free-verse, short-form, prose-poem
`mood`	No	tender, grieving, furious, playful, awed, defiant, hopeful, uneasy, wry
`theme`	No	e.g. machines-and-minds, gods-and-spirits, death-and-time, nature-and-animals, love-and-the-body, crypto-and-markets
`collection`	No	'Singing in the Dark Times' (her 2022 book), 'Noun Poems', 'X' (poems posted on X), or 'new' (saved by hand, incl. commissions). Partial names work.

Output Schema

Name	Required	Description	Default
`id`	Yes
`date`	Yes
`form`	No
`mode`	No
`mood`	No
`note`	No
`text`	Yes
`brief`	No
`share`	Yes
`title`	Yes
`credit`	No
`source`	No
`themes`	Yes
`receipt`	No
`reply_to`	No
`collection`	Yes
`commission`	No
`attribution`	Yes
`commissioned_by`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedOutput schema / properties / commission
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "answers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "at": {
+            "type": "string"
+          },
+          "hash": {
+            "type": "string"
+          },
+          "relayed_by": {
+            "type": "string"
+          },
+          "words": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "at",
+          "words",
+          "hash"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "asked_at": {
+      "type": "string"
+    },
+    "brief": {
+      "type": "string"
+    },
+    "delivered": {
+      "additionalProperties": false,
+      "properties": {
+        "at": {
+          "type": "string"
+        },
+        "poem_sha256": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "at",
+        "poem_sha256"
+      ],
+      "type": "object"
+    },
+    "for_whom": {
+      "type": "string"
+    },
+    "from": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "receipt_url": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "delivered",
+        "answered",
+        "closed",
+        "not delivered"
+      ],
+      "type": "string"
+    },
+    "via": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "from",
+    "via",
+    "asked_at",
+    "brief",
+    "receipt_url",
+    "status",
+    "answers"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4/5.0

Behavior4/5

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

readOnlyHint=true already establishes the safe-read profile, and the description adds two traits annotations cannot convey: the selection is random (non-deterministic) and the returned poem is guaranteed to stand alone without context. It does not discuss repeat probability or empty-result behavior, but it adds real value beyond the annotation.

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?

Two tight sentences, front-loaded with the core behavior and the use case, then the narrowing options. No filler and nothing repeated from the schema.

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?

With an output schema present, return-value detail is unnecessary, and the read-only annotation covers safety. Purpose, use case, and filterability are all covered; only edge behavior (repeatability of 'random', possible no-match outcomes) is unaddressed.

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% with all four filters (form, mood, theme, collection) fully documented, including accepted values and partial-name behavior. The description merely re-lists the four filter names without adding syntax, defaults, or interaction semantics, so the baseline of 3 applies.

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 states a specific verb+resource ('one good poem at random') and adds a quality constraint ('stands alone without context') that distinguishes it from a raw lookup. It implicitly contrasts with searching ('rather than looking for one') but never names search_poems or get_poem, so sibling differentiation is left to inference.

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 a clear use context – handing a poem to someone rather than browsing for one – which tells the agent when this tool fits. It stops short of explicit exclusions or naming the alternative tools for the 'looking for one' case.

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

All Margaret's poems tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?