Skip to main content
Glama

PubSec Radar

by io.github.Kabrawala

Look up an incumbent vendor's federal contracts

incumbent_lookup

Use this to answer "who am I displacing and when?": a vendor name (plus optional agency scope) returns their current and recent awards with values and end dates, flagging awards that end within 12 months as displacement windows. Good queries use the vendor's registered name or a distinctive fragment, e.g. vendor="Booz Allen", agency="DHS". Federal only. Zero results ≠ no presence — check the caveats for name-matching tips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax awards to return (largest first). Default 15.
agencyNoOptional federal agency to scope the lookup, e.g. "DHS". Omit to search government-wide.
vendorYesVendor/incumbent name as registered in federal awards, e.g. "Booz Allen Hamilton", "CACI". FPDS matches it as a phrase — shorter fragments match more.

TDQS

A4.8/5.0
Behavior5/5

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

Without annotations, the description fully discloses behavior: returns current/recent awards with values and end dates, flags those ending within 12 months, notes federal-only scope, and addresses name-matching caveats with zero results.

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 sentences front-load the purpose, provide usage guidance, and address edge cases, with no wasted words.

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?

Despite no output schema, the description fully explains return values (awards with values, end dates, displacement flags) and handles caveats, making the tool self-contained for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds substantial meaning beyond the schema by providing example queries, explaining name matching, and illustrating expected input patterns like vendor='Booz Allen', agency='DHS'.

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 description uses specific verb 'Look up' and resource 'incumbent vendor's federal contracts', and clearly distinguishes from siblings by focusing on displacement windows and answering 'who am I displacing and when?'

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 explicitly states when to use ('to answer who am I displacing and when?') and provides query examples with vendor and agency, but does not explicitly mention when not to use or compare with sibling tools.

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

All PubSec Radar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct task in the federal sales intelligence domain: spending profiles, expiring contracts, discovery questions, incumbent lookup, and opportunity qualification. There is no ambiguity or overlap between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., agency_spend_profile, find_expiring_contracts), making them predictable and easy to navigate.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of public-sector sales intelligence. Each tool adds clear value without superfluous or missing functionality.

Completeness4/5

The set covers essential workflows: agency spend analysis, contract expiration tracking, discovery question generation, incumbent lookup, and deal qualification. Minor gaps like contract search by keyword or agency list exist but do not hinder the primary use cases.

Resources