Skip to main content
Glama
Sign In

GovCon API

by io.github.govconapi
OverviewDiscussionsAdmin

Find who to contact

contact
Read-onlyIdempotent

Who to talk to. Both need the Pro plan.

- company_decision_maker: a company's decision-maker, from its UEI (resolve(company) finds one);
  SAM registration agents are filtered out
- contracting_officer: a contracting officer's details from their name or email; agency and state narrow it

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueiNo
kindYes
nameNo
emailNo
stateNo
agencyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful context beyond that: both modes require the Pro plan, and SAM registration agents are filtered out for decision-maker results. It does not discuss rate limits or error behavior, but with annotations present this is a solid addition.

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 short and front-loaded, with two compact bullets that map to the kind enum. The sentence 'Both need the Pro plan.' is slightly ambiguous about whether it refers to both kinds or both underlying systems, but overall little space is wasted.

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?

Output schema exists, so return values need not be explained. For a six-parameter tool with 0% schema description coverage, the description covers the main semantics and plan requirement, though it could better clarify conditional requiredness and behavior when combined filters are supplied.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: uei is tied to company_decision_maker, name/email identify a contracting officer, and agency/state narrow that result. It does not explicitly restate which parameters are required per kind, but the mapping is inferable from the bullets.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names specific contact-finding modes: company decision-maker and contracting officer. It explains that the tool returns a decision-maker or contracting officer details, which is clear enough to distinguish from generic search/get siblings, though the opening 'Who to talk to' is somewhat informal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The two bullet modes give clear context for choosing between kind values, and the mention of resolve(company) points to an alternative for finding a UEI. However, it does not explicitly say when to use this tool instead of search or get, nor does it state exclusions or prerequisites beyond the Pro plan note.

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

All GovCon API 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