Skip to main content
Glama

Find federal leases that end soon

federal_leases
Read-onlyIdempotent

Buildings and spaces GSA leases for federal agencies whose leases end soon (GSA's Inventory of Owned and Leased Properties, weekly, public domain): address, city, state, rentable square feet, the lease's start and end dates and days left, soonest first, with the count by state and by year. A lease ending is a renewal, a move or a new build-out: early work for janitorial, security, moving, furniture, cabling and construction firms nearby. The end date is a signal: GSA often extends or stays past it; the list names no tenant agency, owner or rent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "federal_leases"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords in the building's name or street address.
cityNoA city, e.g. "Richmond".
limitNoHow many leases to return, 1-50 (default 20).
stateNoA 2-letter state code, e.g. "VA".
monthsNoLeases ending within this many months, 1-60 (default 24).
min_sqftNoSmallest rentable area in square feet, e.g. 20000.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, and the description adds real context beyond that: weekly refresh cadence, public-domain provenance, soonest-first ordering, counts by state and year, and the caveat that GSA often extends or stays past the end date. It also discloses what the data does not contain (tenant agency, owner, rent), which prevents false assumptions.

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?

The content is front-loaded: what it returns comes first, then the commercial use case, then data caveats. It is a bit long, and the trade-by-trade list is slightly padded, but every clause carries information an agent or user would act on.

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 six-parameter, fully documented, output-schema-backed query tool, the description covers scope, source, refresh cadence, ordering, and data limitations. The only mild redundancy is restating return fields that the output schema already defines, and it says nothing about result paging beyond the limit cap.

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 q, city, state, months, min_sqft, and limit with examples. The description reinforces the domain meaning of the filters (ending-soon window, rentable square feet) and notes soonest-first ordering, but adds no syntax, unit, or default detail beyond the schema, so the baseline 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?

The opening clause names a specific verb and resource: GSA leases for federal agencies that end soon, drawn from the Inventory of Owned and Leased Properties. It also states the returned fields (address, city, state, square footage, start/end dates, days left) and the sort order, which is enough to distinguish it from siblings like find_bid_portals or recompetes.

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 use context: a lease ending means a renewal, move, or build-out, which is early work for janitorial, security, moving, furniture, cabling, and construction firms. It does not name an alternative tool or state when not to use it, so it falls short of the top score, but the intended audience and trigger are unambiguous.

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.

Resources