Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Find who to contact

contact
Read-onlyIdempotent

Find the right company decision-maker from a UEI or contracting officer by name, email, agency, or state to identify who to reach for federal procurement outreach.

Instructions

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. Addedv0.2.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds real context beyond them: the Pro plan gate and the fact that SAM registration agents are filtered out of decision-maker results. What it doesn't disclose is what happens when a UEI resolves to multiple people or no person at all.

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 two-sentence preamble plus two bullets is front-loaded and tight; each bullet earns its place by giving the mode's identity and inputs. The phrase 'Both need the Pro plan' is slightly opaque until the bullets are read, but nothing 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?

For a two-mode lookup tool with rich annotations and an output schema, the description covers prerequisites, mode selection, input sourcing, and result filtering. The remaining ambiguity about per-mode parameter applicability is minor and partly resolvable from the enum and output schema.

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?

With 0% schema description coverage, the description must carry all six parameters, and it largely does: kind is explained through the two bullets, uei is tied to resolve(company), name/email are tied to the contracting officer, and agency/state are described as narrowing filters. Gaps remain on expected formats, e.g. whether state takes a full name or a two-letter code, and on which parameters are ignored per kind.

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 the resource (contacts) and enumerates two concrete modes, company_decision_maker and contracting_officer, each with its lookup key. It partially differentiates from siblings by pointing at resolve(company) for obtaining a UEI, though the core verb is only implied by the title rather than stated in the body.

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?

It states which mode to pick and what each requires: a UEI for the decision-maker path (obtained via resolve(company)), a name or email for the contracting officer path, with agency and state as narrowing filters. The Pro plan prerequisite is called out. What's missing is any explicit when-not guidance or routing to the other siblings (get, search, resolve) for adjacent lookups.

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

Deploy Server

Other Tools