Skip to main content
Glama

Hispanic Legacy

by com.hispanic-legacy
OverviewDiscussionsAdmin

Get one Hispanic Legacy knowledge object

get_entity
Read-onlyIdempotent

Fetch one knowledge object by id, with its claims and the sources each claim cites. Use this once search, answer or get_topic has given you an id. An unknown id is not a dead end: the answer names near-miss ids you can retry with.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe knowledge object's id, as returned by search, answer, get_topic or get_related — the last segment of its canonical URL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
entityNo
recoveryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / entity / properties / x
      Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "description": "Indexed instance-specific attributes, grouped by namespace — the same fields api/index.json publishes. Absent when the instance declares none.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"The knowledge object's id, as returned by search, answer, get_topic or get_related — the last segment of its canonical URL."
    • addedOutput schema / properties / entity / properties / media
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "alt": {
+        "type": "string"
+      },
+      "caption": {
+        "type": "string"
+      },
+      "credit": {
+        "type": "string"
+      },
+      "height": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "id": {
+        "type": "string"
+      },
+      "license_spdx": {
+        "type": "string"
+      },
+      "permissions": {
+        "additionalProperties": {
+          "type": "boolean"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "supports": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      },
+      "width": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id",
+      "url",
+      "alt",
+      "credit",
+      "license_spdx",
+      "permissions"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / entity / required
      Previous value: -[
-  "id",
-  "type",
-  "name",
-  "summary",
-  "tags",
-  "evidence_tier",
-  "confidence",
-  "last_verified",
-  "canonical_url",
-  "api_url",
-  "questions",
-  "claims"
-]New value: +[
+  "id",
+  "type",
+  "name",
+  "summary",
+  "tags",
+  "evidence_tier",
+  "confidence",
+  "last_verified",
+  "canonical_url",
+  "api_url",
+  "questions",
+  "claims",
+  "media"
+]
  3. Changed1 schema field changed
    • addedOutput schema / properties / recovery
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "available": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "available_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "available_truncated": {
+      "type": "boolean"
+    },
+    "did_you_mean": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "next_tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "available_count",
+    "available",
+    "next_tool",
+    "hint"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, and the description adds useful extra context: the structure of the returned data, the prerequisite that an id comes from a prior tool, and the error-recovery behavior where unknown ids produce near-miss retry candidates. There is no contradiction with 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 three sentences, each earning its place: the core operation, the workflow trigger, and the error-recovery behavior. There is no filler or repetition, and the most important information is front-loaded.

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 simple single-parameter read-only lookup with an output schema available, the description covers purpose, usage context, and failure behavior. The output schema handles return structure, so 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?

The input schema describes the single parameter 'id' in full detail, including where it comes from and its URL format, so schema coverage is 100%. The description only says 'by id,' adding no meaningful semantic information beyond the schema. Baseline 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 verb and resource: 'Fetch one knowledge object by id,' and further specifies the return content ('with its claims and the sources each claim cites'). This is concrete enough to distinguish it from sibling tools like get_overview or get_sources, even without naming them.

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 an explicit trigger: 'Use this once search, answer or get_topic has given you an id,' which clearly establishes a workflow context. It also provides failure-recovery guidance for unknown ids. However, it does not explicitly mention when not to use this tool or name alternative siblings for different needs, so it stops short of full exclusionary guidance.

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

All Hispanic Legacy 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