govcon-contractor-signals

contractor_signals

Given a federal contractor NAME, return its acquisition-likelihood / rising-contractor signal profile: a 0-100 pattern-based score with full reasoning, plus award-velocity, multi-year trajectory, agency/NAICS mix, biggest win, set-aside footprint, and (if public) SEC EDGAR ticker + recent corporate-event filings. Built on PUBLIC USAspending.gov + EDGAR data. Probabilistic leading-signal estimate — NOT certainty, NOT insider/MNPI, NOT investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Contractor name, e.g. 'Palantir' or 'ECS Federal'.

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description fully discloses behavioral traits: it is a probabilistic leading-signal estimate, not certainty, not insider information, based on public USAspending.gov and EDGAR data. This helps the agent understand the tool's limitations and data sources.

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 description is well-structured, starting with the primary output, then data sources, then caveats. It is slightly long but every sentence adds necessary information.

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?

Given no output schema, the description comprehensively lists what is returned (score, reasoning, award-velocity, trajectory, agency mix, etc.). It covers key aspects but could specify output format for better parsing.

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

Parameters4/5

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

The sole parameter 'name' has a clear schema description with an example. The tool description elaborates on how the name is used, adding context beyond the schema. Since schema coverage is 100% and the parameter is simple, the description adds value.

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 clearly states the tool takes a contractor name and returns a detailed signal profile, including acquisition-likelihood score, reasoning, award-velocity, trajectory, and more. It is distinct from sibling tools 'rising_contractors' and 'search_awards', which focus on listing rising contractors and searching awards respectively.

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 indicates when to use: given a federal contractor NAME. It provides context that the data is public and the signal is probabilistic, not investment advice. However, it does not explicitly state when not to use or suggest alternatives.

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

All govcon-contractor-signals tools Inspect

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

A3.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: one retrieves a detailed signal profile for a specific contractor, one provides a ranked feed of rising contractors, and one searches federal awards. No overlap or ambiguity.

Naming Consistency3/5

Tool names follow a general pattern of lowercase snake_case, but the stylistic role varies: 'contractor_signals' is a noun phrase, 'rising_contractors' is adjective-noun, and 'search_awards' is verb-noun. This inconsistency, while minor, breaks a strict verb_noun pattern.

Tool Count4/5

Three tools is appropriate for the focused domain of government contractor signals and award data. The count is minimal but covers the key operations: individual signal, aggregated feed, and search. Could arguably benefit from one or two additional tools (e.g., detailed award view), but not excessive.

Completeness4/5

The tools cover the primary use cases: retrieving an individual signal profile, accessing a ranked feed, and searching awards. However, there is no tool to retrieve detailed information on a specific award or to filter signals by criteria beyond what is embedded in the tools. This is a minor gap but does not severely hinder functionality.

Resources

Need Help?