GovGazette

Read exclusion evidence

exclusion_context

Read-onlyIdempotent

Retrieve an exclusion with agency explanation, named restriction references, source evidence, explicit source-age warnings and supported business links.

Input Schema

Name	Required	Description	Default
`id`	Yes	Stable exclusion record ID returned by search_exclusions or check_exclusions.
`generation`	No	Retained snapshot UUID; omit for the current snapshot.

Output Schema

Name	Required	Description
`id`	Yes
`data`	Yes
`text`	Yes
`title`	Yes
`coverage`	Yes	Dated SAM source coverage.
`collection`	Yes
`generation`	Yes
`text_length`	Yes
`text_has_more`	Yes
`business_context`	Yes	Supported vendor and award links, with match basis.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

addedOutput schema / $defs / SourceFreshness / properties / attention_required
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / $defs / SourceFreshness / properties / warn_age_seconds

Added value: +{
+  "description": "Early-warning boundary, separate from the stale-source boundary.",
+  "format": "int64",
+  "type": "integer"
+}

changedOutput schema / $defs / SourceFreshness / required

Previous value: -[
-  "state",
-  "evaluated_at",
-  "max_age_seconds"
-]New value: +[
+  "state",
+  "evaluated_at",
+  "max_age_seconds",
+  "warn_age_seconds",
+  "attention_required"
+]

Changed4 schema fields changedOct 6, 2026

addedOutput schema / $defs / ExclusionCoverage

Added value: +{
+  "properties": {
+    "freshness": {
+      "$ref": "#/$defs/SourceFreshness",
+      "description": "Fresh, stale, unknown or unavailable, with age and the 24-hour warning policy."
+    },
+    "observed_at": {
+      "description": "Observation time does not replace the official source timestamp.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scope": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Present as unavailable when no SAM coverage exists in this generation.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "freshness"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / FreshnessState

Added value: +{
+  "enum": [
+    "fresh",
+    "stale",
+    "unknown",
+    "unavailable"
+  ],
+  "type": "string"
+}

addedOutput schema / $defs / SourceFreshness

Added value: +{
+  "properties": {
+    "evaluated_at": {
+      "description": "UTC time when age was evaluated; source and observation dates are unchanged.",
+      "type": "string"
+    },
+    "max_age_seconds": {
+      "description": "Explicit warning threshold for this daily snapshot. Not a scheduler promise.",
+      "format": "int64",
+      "type": "integer"
+    },
+    "source_age_seconds": {
+      "description": "Age of the official source timestamp, never the import or enrichment timestamp.",
+      "format": "int64",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "state": {
+      "$ref": "#/$defs/FreshnessState"
+    },
+    "warning": {
+      "description": "User-facing warning, or null when within the warning threshold.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state",
+    "evaluated_at",
+    "max_age_seconds"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / coverage / $ref

Previous value: -"#/$defs/JsonObject"New value: +"#/$defs/ExclusionCoverage"

Changed3 schema fields changedSep 24, 2026

addedInput schema / properties / generation / description

Added value: +"Retained snapshot UUID; omit for the current snapshot."

addedInput schema / properties / id / description

Added value: +"Stable exclusion record ID returned by search_exclusions or check_exclusions."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "JsonObject": {
+      "description": "Source-specific JSON map. The envelope is stable; map keys vary by official source.",
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "business_context": {
+      "$ref": "#/$defs/JsonObject",
+      "description": "Supported vendor and award links, with match basis."
+    },
+    "collection": {
+      "type": "string"
+    },
+    "coverage": {
+      "$ref": "#/$defs/JsonObject",
+      "description": "Dated SAM source coverage."
+    },
+    "data": {
+      "$ref": "#/$defs/JsonObject"
+    },
+    "generation": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "text_has_more": {
+      "type": "boolean"
+    },
+    "text_length": {
+      "format": "uint",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "generation",
+    "collection",
+    "id",
+    "title",
+    "text",
+    "data",
+    "text_length",
+    "text_has_more",
+    "coverage",
+    "business_context"
+  ],
+  "type": "object"
+}

AddedSep 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. Description adds what the record contains (explicit source-age warnings), which is useful beyond annotations, but omits error behavior when ID is stale or missing and snapshot semantics beyond the schema.

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?

One dense sentence listing exactly the output components, front-loaded with the core action; no filler.

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?

Output schema exists, so return structure needn't be explained. Description plus annotations plus 100% param coverage makes the tool callable, though a note on missing/stale records would complete the behavioral picture.

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 coverage is 100%, so the schema already explains 'id' and 'generation'. The description adds no information about parameter behavior, so 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?

Specific verb 'Retrieve' with resource 'exclusion' and enumerated payload contents (agency explanation, restriction references, source evidence, source-age warnings, business links). Clearly distinguishable from search_exclusions (which returns IDs) and exclusion_changes (which tracks changes) by emphasizing full evidence retrieval.

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?

Implied usage via schema reference ('ID returned by search_exclusions or check_exclusions') hints at the follow-up workflow, but the description itself offers no explicit when-to-use vs exclusion_changes or detail.

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

All GovGazette 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.