Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Resolve names to IDs

resolve
Read-onlyIdempotent

Converts agency names, NAICS terms, company names, DUNS numbers, or organization names into the exact IDs and codes required by GovCon search and entity tools.

Instructions

Turn what the user said into the IDs and codes the other tools take. Start here when the user names an agency, describes their work, or names a company.

  • agency: an agency name or acronym ("Navy", "FEMA") -> the exact agency value search filters expect

  • naics: words from NAICS titles ("computer", "engineering", "construction") -> matching codes with market size. It matches titles, not topics: for "cybersecurity" try "computer"

  • company: a company name -> SAM registrations with their UEI (a large firm has several; pick by name and location, or use search(companies), Pro, which ranks by award history)

  • identifier: a legacy 9-digit DUNS number -> the matching UEI and company (a CAGE code goes to get(entity))

  • organization: an agency or sub-agency name -> its organization_id in the federal hierarchy

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>",
      "query": "<query>"
    },
    "name": "resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: NAICS matching is title-based rather than topic-based, companies often have multiple UEIs requiring name/location disambiguation, and DUNS input yields a UEI plus company. It stops short of describing what happens on zero or ambiguous matches.

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?

Front-loaded with the one-line purpose and the 'start here' trigger, followed by a scannable bullet per enum value. No filler sentences; the examples and sibling pointers all serve invocation decisions.

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?

Two required parameters, one enum, an output schema already present, and every enum branch explained with inputs and expected returns. An agent has everything needed to pick the right `kind` and phrase the `query` correctly.

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?

Schema coverage is 0%, so the description carries the full burden and does: each of the five `kind` enum values is defined with example input and the shape of the return it maps to. The `query` parameter is given per-kind meaning (free text, acronym, title words, DUNS digits), which is well beyond the bare string type in the schema.

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: turning user-mentioned names into the IDs/codes that other tools consume. It explicitly positions itself relative to siblings ("pick by name and location, or use search(companies)", "a CAGE code goes to get(entity)"), so an agent can distinguish resolve from search and get without opening any schema.

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?

Gives an explicit entry condition ("Start here when the user names an agency, describes their work, or names a company") plus per-kind routing rules and named alternatives for cases that should go elsewhere (CAGE codes to get, ranked company lookup to search(companies), Pro).

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