Skip to main content
Glama

Irish History: 1798, O'Connell, Young Ireland & the Great Famine

by com.spencerhofmans
OverviewDiscussionsAdmin

Find an Irish Historical Figure

get_historical_figure
Read-onlyIdempotent

Find passages about a named historical figure in Spencer Hofmans' Irish history guides. Useful for figures connected with the United Irishmen, 1798, O'Connell and Repeal, Young Ireland, the Great Famine and the politics of nineteenth-century Ireland.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull or commonly used name of the historical figure, for example Henry Joy McCracken, Daniel O'Connell or Thomas Davis.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
errorNo
foundYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / error
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / related_historical_fiction
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "amazon_url": {
-        "type": "string"
-      },
-      "author": {
-        "type": "string"
-      },
-      "historical_guide_url": {
-        "type": "string"
-      },
-      "note": {
-        "type": "string"
-      },
-      "relationship": {
-        "type": "string"
-      },
-      "title": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "title",
-      "author",
-      "relationship",
-      "amazon_url",
-      "historical_guide_url",
-      "note"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • changedOutput schema / properties / results / items / properties / section / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedOutput schema / required
      Previous value: -[
-  "name",
-  "found",
-  "results",
-  "related_historical_fiction"
-]New value: +[
+  "name",
+  "found",
+  "results"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "found": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "related_historical_fiction": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amazon_url": {
+            "type": "string"
+          },
+          "author": {
+            "type": "string"
+          },
+          "historical_guide_url": {
+            "type": "string"
+          },
+          "note": {
+            "type": "string"
+          },
+          "relationship": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "author",
+          "relationship",
+          "amazon_url",
+          "historical_guide_url",
+          "note"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "author": {
+            "type": "string"
+          },
+          "guide": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "passage": {
+            "type": "string"
+          },
+          "section": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source_url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "guide",
+          "section",
+          "passage",
+          "source_url",
+          "author"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "name",
+    "found",
+    "results",
+    "related_historical_fiction"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already convey read-only, idempotent, open-world, and non-destructive behavior, so the description only needs to add context. It adds the corpus limitation (passages within Spencer Hofmans' guides) and the historical focus, which help set expectations. There is no contradiction with the annotations.

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?

The description is two sentences with no fluff. The operation and corpus are front-loaded, and the second sentence adds genuinely useful topical scope without redundancy.

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?

Given the tool has a single required parameter, an output schema, and read-only annotations, the description covers the essential context: what is searched, whose guides are searched, and which historical topics are relevant. It could mention empty-result behavior for figures outside the guides, but the open-world hint and output schema mitigate that gap.

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 the name parameter clearly documented and given examples. The description reinforces that the parameter refers to a named historical figure and connects it to the guide corpus, but it does not add substantive details beyond the schema's own description.

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 action and resource: 'Find passages about a named historical figure in Spencer Hofmans' Irish history guides.' It clearly identifies the tool's scope but does not explicitly contrast it with siblings like search_history or get_guide, so it falls short of full differentiation.

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?

The second sentence gives useful topical context, indicating the tool is suited to figures associated with the United Irishmen, 1798, O'Connell and Repeal, Young Ireland, and the Great Famine. However, it does not state when this tool should be avoided or name sibling alternatives, leaving usage guidance implied rather than explicit.

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

All Irish History: 1798, O'Connell, Young Ireland & the Great Famine toolsInspect
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