Skip to main content
Glama

Ny Procurement Awards

ny_procurement_awards
Read-onlyIdempotent

Search NEW YORK STATE government contract awards & procurement from the official Procurement Report for State Authorities on data.ny.gov (the section 2800 Public Authorities Law filings collected by the NY Authorities Budget Office). Each result is a procurement contract awarded by a New York State authority (the awarding agency) with the winning vendor, the contract dollar amount, the procurement type, the award/solicitation process, the description of goods/services, and award/begin dates. Filter by vendor, awarding agency/authority, keyword, procurement type, fiscal year, and/or a minimum amount; results are ranked by contract amount (biggest awards first) by default. Use this for questions like "who won the biggest New York State contracts", "top vendors to the Metropolitan Transportation Authority", or "NY state software contracts". This is NEW YORK STATE data (not federal, not New York City).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "agency": "Metropolitan Transportation Authority",
      "vendor": "IBM"
    },
    "name": "ny_procurement_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: "amount" = largest contract first (default), "date" = most recent award date first.
limitNoMax records to return (default 20, max 100).
agencyNoAwarding NY State authority / agency name (case-insensitive substring), e.g. "Metropolitan Transportation Authority", "Power Authority", "Dormitory Authority".
offsetNoNumber of records to skip for pagination (default 0).
vendorNoWinning vendor name to match (case-insensitive substring), e.g. "IBM", "Turner Construction".
keywordNoCase-insensitive substring to match against the procurement description, e.g. "software", "construction", "consulting".
min_amountNoOnly return awards whose contract amount is at least this many dollars, e.g. 1000000.
fiscal_yearNoReporting fiscal year (calendar year of the fiscal-year-end date), e.g. 2022. Matches contracts whose fiscal_year_end_date falls in that year.
procurement_typeNoProcurement type substring, e.g. "Technology - Software", "Construction", "Consulting Services", "Commodities/Supplies".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered; the description still adds real context about provenance (official ABO filings on data.ny.gov) and default behavior (results ranked by contract amount, biggest first). It stops short of stating pagination mechanics or result caps, though the schema covers limit/offset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with source and scope, then filters, then example queries, which is a sensible order for an agent scanning quickly. The long parenthetical about section 2800 filings and the triple-negative scoping sentence add bulk that could be trimmed without losing meaning.

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?

With 9 optional parameters and no output schema, the description compensates by listing the fields each result carries (vendor, amount, procurement type, award process, goods/services description, dates), so the agent knows what comes back. Combined with full schema coverage and clear scope limits, nothing needed to invoke it correctly 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%, so the schema already explains every filter including the sort enum and the fiscal-year-end matching rule. The description's enumeration of filters and its note that results default to amount ranking largely restate the schema rather than adding syntax or edge-case meaning.

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 and resource ("Search NEW YORK STATE government contract awards & procurement") and pins down the exact source (section 2800 Public Authorities Law filings via data.ny.gov / NY Authorities Budget Office). It explicitly bounds the domain with "This is NEW YORK STATE data (not federal, not New York City)," so an agent can distinguish it from adjacent procurement or entity tools.

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 concrete when-to-use triggers via example questions ("who won the biggest New York State contracts", "top vendors to the Metropolitan Transportation Authority") plus scope exclusions for federal and NYC data. The gap is that it never routes the agent to a named alternative such as ny_procurement_vendor, which appears to overlap on vendor-oriented queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.