Skip to main content
Glama
Sign In

Gsa Elibrary

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gsa Schedule Contract Holders

gsa_schedule_contract_holders
Read-onlyIdempotent

List Multiple Award Schedule contract holders for a given SIN (Special Item Number), optionally narrowed by a keyword matched against contractor name, contract number, city, or state. Returns each holder's contract number, phone, and location. Use gsa_schedule_search first to find a valid schedule/SIN pair.

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": "541511",
      "limit": 5,
      "schedule": "MAS"
    },
    "name": "gsa_schedule_contract_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinYesSpecial Item Number (SIN), e.g. "541511" or "ALL 2"
limitNoMax holders to return (default 25, max 100)
offsetNoPagination offset (default 0)
keywordNoOptional filter against contractor name, contract number, city, or state
scheduleNoSchedule/GWAC number the SIN belongs to (default "MAS")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety bar is low. The description adds value by naming the returned fields (contract number, phone, location) and the lookup prerequisite, which matters because there is no output schema; it does not mention pagination or result caps in prose.

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?

Three tight sentences: scope first, return fields second, prerequisite last. Every sentence carries information an agent needs and nothing is padded.

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?

Covers purpose, prerequisite, and partial return shape despite having no output schema. The remaining gap, pagination and how to page through large holder lists, is handled by the schema's limit/offset fields rather than prose.

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 five parameters. The description restates the SIN scoping and keyword matching semantics but adds nothing about limit, offset, or the schedule default that the schema does not already say.

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 (List) and resource (Multiple Award Schedule contract holders) scoped to a SIN, plus the optional narrowing dimension. It is clearly distinguishable from gsa_schedule_search, which it references as the prerequisite lookup tool.

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?

Explicitly instructs the agent to run gsa_schedule_search first to obtain a valid schedule/SIN pair, which is a real prerequisite that prevents errors. It does not, however, address when to use gsa_contractor_profile instead for holder details.

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