Skip to main content
Glama
govconapi

io.github.govconapi/govconapi

Official

Search Contacts

search_contacts
Read-onlyIdempotent

Find a federal contracting officer's contact details by name (with optional agency/state) or exact email. Use it to get the buyer-side phone, agency, and name for teaming or capture.

Instructions

Look up a CONTRACTING OFFICER's contact info, the buyer side, distinct from get_company_contact (the vendor/teammate side).

Capture & Teaming tool, Pro only (`contacts_access`). A RESOLVER, not a directory, you cannot list/browse all contacts through this tool, only look up a specific one.

Two modes, provide one:
- name (+ optional agency, state for disambiguation): substring match, returns up to 5
- email: exact match, returns one record, useful when you already have an email on
  file and want the current name/agency/phone for it

Returns 404 if nothing matches, 402 if the caller's plan doesn't include contacts_access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
emailNo
stateNo
agencyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds substantial behavior beyond annotations: it is a resolver, not a browseable directory, name searches are substring matches returning up to 5, email searches are exact matches returning one record, and it documents 404 and 402 error conditions. This goes beyond the readOnly/idempotent hints.

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?

The description is front-loaded with the core identity and key differentiator, then uses compact bulleted modes and error cases. Every sentence adds operational value with no filler.

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?

Covers identity, access requirements, mode selection, expected result counts, and error codes. Output schema exists so return value details are not needed in the description. Complete enough for correct invocation and troubleshooting.

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 has 0% description coverage, so the description must carry the meaning. It explains name (substring match), email (exact match), and the disambiguation role of agency/state. It does not define value formats, but the schema already marks them as plain optional strings.

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?

States a specific verb and resource: look up a CONTRACTING OFFICER's contact info, and explicitly distinguishes itself from get_company_contact. The buyer-side framing makes the purpose immediately obvious and differentiates it from a large sibling list.

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

Usage Guidelines5/5

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

Explicitly names the sibling tool it is not and gives the selection criterion (buyer vs vendor/teammate side). It also describes two exclusive modes with clear conditions for choosing name vs email, including disambiguation via agency/state.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/govconapi/govconapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server