Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Recent federal contract awards (USAspending)

federal_awards_recent
Read-onlyIdempotent

Recently signed U.S. federal new awards from USAspending.gov, newest first. Returns the newest 25 by default (set limit; page with offset); total_matched reports the full count. Optional min_amount (USD floor) and days (last-N-days window). Every award carries its source award_url; awards without a source link are dropped and never returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOnly awards signed within the last N days.
limitNoMax rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap.
offsetNoRows to skip before this page (pagination). Default 0.
min_amountNoOnly awards at or above this USD amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Only awards signed within the last N days.",
+  "type": "integer"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max awards to return (default 50)"New value: +"Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Rows to skip before this page (pagination). Default 0.",
+  "type": "integer"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds real behavioral context beyond them: newest-first ordering, default page size, pagination contract via total_matched, limit<=0 meaning no cap, and the non-obvious filtering rule that awards without a source link are silently dropped and never returned.

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?

Three compact sentences, front-loaded with what the tool returns and then the paging/filtering behavior. Every clause carries information; nothing is padding.

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?

No output schema exists, so the description compensates by naming the key response fields (total_matched, award_url) and disclosing the drop rule for awards lacking a source link. An agent has enough to call it correctly and interpret the result.

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%, so the schema already documents all four parameters including defaults, pagination semantics, and the no-cap rule. The description restates those same points (limit/offset/total_matched, min_amount USD floor, days window) without adding syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb+resource+scope: 'recently signed U.S. federal new awards from USAspending.gov, newest first.' It also clarifies sort order and data source in the first clause, which is everything needed to distinguish it from the insider/13F/activist siblings.

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?

Gives clear operational context (default 25, page with offset, total_matched for full count) and notes the optional min_amount and days filters. It does not name a sibling alternative or an explicit when-not condition, but the sibling set is an entirely different domain, so the routing risk is low.

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

All Insider Buy Signals 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