Hispanic Legacy

Sources behind Hispanic Legacy

get_sources

Read-onlyIdempotent

The instance's source registry — each entry with its evidence tier, reliability and access date. PAGED: 25 entries by default, 200 at most, and a response budget of about 64 KB per call — a page over budget comes back shorter WITH a next_cursor, never truncated. Read next_cursor and call again to continue; its absence means you have the last page. Filter by object_id, tier, host or accessed_since to avoid paging through a registry you do not need. Use this when you need the registry entry behind a citation, or a sample of the whole registry to judge the corpus before trusting it; get_entity already tells you which sources a claim cites.

Input Schema

TableJSON Schema

Name	Required	Description
`host`	No	Only sources whose URL is served by this host, compared without a leading www. A source with no URL never matches.
`tier`	No	Only sources of this evidence tier, spelled exactly as get_sources reports it.
`limit`	No	How many entries to return. Defaults to 25.
`cursor`	No	Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one.
`object_id`	No	Restrict the answer to the sources cited by this knowledge object. Omit it to page the whole registry.
`accessed_since`	No	Only sources accessed on or after this ISO date (YYYY-MM-DD).

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`total`	Yes	How many sources matched the filters, before paging.
`sources`	Yes
`recovery`	No
`returned`	Yes
`next_cursor`	No	Pass to the next call to continue. ABSENT means this was the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 6, 2026

addedInput schema / properties / accessed_since

Added value: +{
+  "description": "Only sources accessed on or after this ISO date (YYYY-MM-DD).",
+  "maxLength": 10,
+  "minLength": 4,
+  "type": "string"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / host

Added value: +{
+  "description": "Only sources whose URL is served by this host, compared without a leading www. A source with no URL never matches.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "How many entries to return. Defaults to 25.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / object_id / description

Previous value: -"Restrict the answer to the sources cited by this knowledge object. Omit it to get the instance's whole source registry."New value: +"Restrict the answer to the sources cited by this knowledge object. Omit it to page the whole registry."

addedInput schema / properties / tier

Added value: +{
+  "description": "Only sources of this evidence tier, spelled exactly as get_sources reports it.",
+  "maxLength": 60,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "description": "Pass to the next call to continue. ABSENT means this was the last page.",
+  "type": "string"
+}

addedOutput schema / properties / returned

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "How many sources matched the filters, before paging.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "found",
-  "sources"
-]New value: +[
+  "found",
+  "sources",
+  "total",
+  "returned"
+]

Changed1 schema field changedSep 1, 2026

addedInput schema / properties / object_id / description

Added value: +"Restrict the answer to the sources cited by this knowledge object. Omit it to get the instance's whole source registry."

Changed1 schema field changedAug 26, 2026

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"
+}

First observedAug 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond the schema: pagination details (25 default, 200 max, ~64 KB budget, over-budget pages come back shorter WITH next_cursor, never truncated), how to detect the last page, and the semantics of a source with no URL never matching a host filter. This is rich behavioral disclosure.

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 compact and front-loaded: a one-sentence definition, then pagination semantics, then filtering guidance, then usage routing. Every sentence earns its place and none are redundant with the schema.

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 read-only list tool with an output schema and 100% schema coverage, the description fully covers what an agent needs: what the resource is, when to use it versus siblings, how pagination works, and how to narrow results. The output schema covers return values, so nothing critical 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?

Schema description coverage is 100%, and each parameter has a meaningful schema description (e.g., cursor is 'Opaque; do not construct one', host has 'A source with no URL never matches'). The description adds the pagination context (next_cursor meaning, page budget) but doesn't need to repeat parameter-level details. Baseline 3 is appropriate since the schema already carries the full weight.

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+resource ('The instance's source registry') and immediately distinguishes it from siblings by saying 'Use this when you need the registry entry behind a citation, or a sample of the whole registry... get_entity already tells you which sources a claim cites.' It clearly identifies the resource as a source registry and its role relative to get_entity.

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

Usage Guidelines5/5

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

Explicit when-to-use: 'Use this when you need the registry entry behind a citation, or a sample of the whole registry to judge the corpus before trusting it; get_entity already tells you which sources a claim cites.' It also gives filtering advice ('Filter by object_id, tier, host or accessed_since to avoid paging') which is practical usage 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 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.