Agent Einstein — Crypto & Market Intelligence

US Government Contract Awards

get_government_contracts

Read-onlyIdempotent

Recent notable US federal contract awards — useful for tracking which public companies are winning government money.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1-25).

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Awards in this pass.
`limit`	No	Row cap applied to every list in this payload.
`stale`	No	True when the snapshot is past its refresh interval.
`reason`	No	Why the payload is absent, when `available` is false.
`shorts`	No	Short signals.
`sources`	No	Per-source status — which award feeds answered.
`topScore`	No	Its score, 0-1.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`fetchedAt`	No	When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries.
`topSector`	No	Its sector.
`topTicker`	No	Highest-scoring ticker.
`longSignals`	No	Scored buy-side signals.
`shortSignals`	No	Scored sell-side signals; same fields as `longSignals`.
`actionableLongs`	No	Long signals that cleared the scoring gate.
`sectorAggregates`	No	Awarded dollars by sector.
`watchlistExpansion`	No	Tickers the pass added to the watchlist.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "actionableLongs": {
+      "description": "Long signals that cleared the scoring gate."
+    },
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "count": {
+      "description": "Awards in this pass."
+    },
+    "fetchedAt": {
+      "description": "When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."
+    },
+    "limit": {
+      "description": "Row cap applied to every list in this payload.",
+      "type": "number"
+    },
+    "longSignals": {
+      "description": "Scored buy-side signals.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "awardedAt": {
+            "description": "Award date."
+          },
+          "band": {
+            "description": "Score band."
+          },
+          "direction": {
+            "description": "long or short."
+          },
+          "fundamentalsConfluence": {
+            "description": "Whether fundamentals agree with the award signal."
+          },
+          "hasFms": {
+            "description": "True when a Foreign Military Sale is attached."
+          },
+          "headline": {
+            "description": "One-line summary."
+          },
+          "primaryTicker": {
+            "description": "Lead ticker."
+          },
+          "rationale": {
+            "description": "Why it scored where it did."
+          },
+          "score": {
+            "description": "Conviction score, 0-1."
+          },
+          "sector": {
+            "description": "Sector."
+          },
+          "surpriseRatio": {
+            "description": "Award size against the contractor’s run rate."
+          },
+          "tickers": {
+            "description": "Every ticker on the award.",
+            "items": {},
+            "type": "array"
+          },
+          "totalUsd": {
+            "description": "Awarded USD."
+          }
+        }
+      },
+      "type": "array"
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "sectorAggregates": {
+      "description": "Awarded dollars by sector.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "awardCount": {
+            "description": "Awards."
+          },
+          "sector": {
+            "description": "Sector."
+          },
+          "topTickers": {
+            "description": "Tickers carrying the sector.",
+            "items": {},
+            "type": "array"
+          },
+          "totalUsd": {
+            "description": "Awarded USD."
+          }
+        }
+      },
+      "type": "array"
+    },
+    "shortSignals": {
+      "description": "Scored sell-side signals; same fields as `longSignals`.",
+      "items": {},
+      "type": "array"
+    },
+    "shorts": {
+      "description": "Short signals."
+    },
+    "sources": {
+      "additionalProperties": true,
+      "description": "Per-source status — which award feeds answered."
+    },
+    "stale": {
+      "description": "True when the snapshot is past its refresh interval."
+    },
+    "topScore": {
+      "description": "Its score, 0-1."
+    },
+    "topSector": {
+      "description": "Its sector."
+    },
+    "topTicker": {
+      "description": "Highest-scoring ticker."
+    },
+    "watchlistExpansion": {
+      "description": "Tickers the pass added to the watchlist.",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'recent notable' awards, but does not disclose update frequency, data source, or whether 'notable' implies filtering or ranking. This is acceptable for a read-only list tool but does not go beyond the annotations meaningfully.

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?

A single sentence conveys the core data and the most relevant use case with no filler. It is front-loaded with the subject matter and immediately useful to an agent deciding whether to call the tool.

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?

For a simple, read-only, single-parameter tool with an output schema, the description is largely sufficient. It gives the subject and purpose, and the annotations cover the operational safety hints. A minor gap is that 'notable' is undefined, but this does not prevent a correct call.

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%: the lone parameter, limit, is fully documented with type, default, and range. The description adds no parameter-specific information, but none is needed because the schema already handles it.

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 clearly identifies the resource ('US federal contract awards') and the use case ('tracking which public companies are winning government money'), which differentiates it from siblings like get_congress_trades. It lacks an explicit verb such as 'retrieve' or 'list,' but the name and title make the action unambiguous.

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?

The description gives a clear context for use: tracking notable federal contract wins by public companies. It does not explicitly name alternatives or state when not to use it, but among the siblings, no other tool covers government contract awards directly, so the intended usage is reasonably clear.

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

All Agent Einstein — Crypto & Market Intelligence 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.