Skip to main content
Glama
Sign In

Gsa Elibrary

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gsa Schedule Search

gsa_schedule_search
Read-onlyIdempotent

Search GSA eLibrary by keyword, SIN number, NAICS code, or contractor/manufacturer name. Returns matching Multiple Award Schedule (MAS) categories/SINs and contractor matches with contract numbers — the starting point for finding who holds a GSA schedule contract.

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": {
      "keyword": "cybersecurity"
    },
    "name": "gsa_schedule_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword, SIN/category number, NAICS code, contract number, or contractor/manufacturer name
search_typeNoHow to match multi-word keywords (default all_words)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, open-world search operation. The description adds that results include MAS categories/SINs and contractor matches with contract numbers, but it omits useful behavior details such as result limits, pagination, or the nature of the external eLibrary lookup.

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 two concise sentences, front-loaded with the search scope and followed by the return-value summary. It contains no filler and is appropriately sized for a simple two-parameter search tool.

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 read-only search tool with full schema coverage and no output schema, the description provides enough to understand the searchable fields and the general shape of results. It could be stronger by naming alternative GSA tools or noting result limits, but the core context is present.

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%, and the schema already documents both keyword and search_type. The description restates the keyword types but does not add new semantics, such as how search_type interacts with keyword or examples of matching behavior.

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 gives a clear verb and resource: search GSA eLibrary by keyword, SIN, NAICS, or contractor name, returning MAS categories/SINs and contractor matches. It is clear, but it does not explicitly distinguish itself from sibling tools like gsa_schedule_contract_holders or gsa_contractor_profile beyond calling itself a starting point.

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

Usage Guidelines3/5

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

The phrase 'starting point for finding who holds a GSA schedule contract' implies this should be used before more specific lookups. However, it does not explicitly state when to use this tool versus gsa_schedule_contract_holders, gsa_contractor_profile, or other GSA-related siblings.

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