Skip to main content
Glama
Sign In

Gsa Elibrary

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gsa Contractor Profile

gsa_contractor_profile
Read-onlyIdempotent

Look up which GSA Multiple Award Schedule(s)/GWAC(s) a contractor holds and its contract number(s) on each. Pass a known sin (and schedule) to also pull phone/city/state from that SIN's contract-holder listing. Address, email, website, SAM UEI, NAICS, socio-economic/exclusion-list status, and option-period end date are not available from this tool — eLibrary's per-contract detail page that carries them is blocked from our network; the response names this plainly.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sin": "ALL 2",
      "schedule": "ALIAN2",
      "contractor_name": "BOOZ ALLEN HAMILTON INC"
    },
    "name": "gsa_contractor_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinNoOptional — a Special Item Number already known to be held by this contractor (e.g. from gsa_schedule_search), used to additionally pull phone/city/state
scheduleNoSchedule/GWAC number the `sin` belongs to (default "MAS"); only used when `sin` is given
contract_numberNoOptional — narrow to one specific contract number when the contractor holds several
contractor_nameYesContractor/manufacturer name (matched case-insensitively against eLibrary's search results)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable context about a network-level limitation on eLibrary's per-contract detail page and notes that the response names the missing fields plainly, which goes beyond the annotations.

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 purpose and uses every sentence for useful information: core lookup behavior, optional SIN-based enrichment, and unavailable fields. There is no redundant or low-value content.

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 four parameters, full schema coverage, annotations, and no output schema, the description is largely complete. It explains the main output and explicitly manages expectations about unavailable fields, though it could say more about return shape or result limits.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters, including optionality and the default `schedule` value. The description reinforces the `sin`/`schedule` enrichment behavior but adds little beyond what the schema provides.

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 states a specific verb and resource: look up which GSA MAS/GWAC a contractor holds and its contract numbers on each. It is clear what the tool does, but it does not explicitly distinguish itself from siblings like gsa_schedule_search or gsa_schedule_contract_holders.

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 gives clear usage context, including when to pass a known `sin`/`schedule` to enrich results with phone/city/state, and lists data that cannot be retrieved from this tool. However, it does not explicitly name sibling alternatives or state when to use them instead.

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

All Gsa Elibrary 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