Skip to main content
Glama

Show results

show_results
Read-onlyIdempotent

Use this last, after searching, to show the user the opportunities you picked as a card. Pass up to 10 ids from search_contracts or search_grants results, best first. Keep your reply to a short summary; the card shows the rows.

Ids from search_jobs and award ids (search_awards, get_company) are not shown. Do not use to search (search_contracts, search_grants) or for one result's details (get_opportunity).

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": {
      "ids": "<ids>"
    },
    "name": "show_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds from search_contracts or search_grants results (not award ids), in the order to show them.

Output Schema

NameRequiredDescriptionDefault
noteNo
as_ofNoWhen the API generated the first row shown (ISO time).
failedNoIds not fetched because MatchAwards was busy or failed. Call show_results again with just these ids to add them.
missingNoIds not shown because they were not found or are not a contract or grant (a job). Retrying will not add them.
resultsYes
warningNoSet when some ids could not be fetched (see failed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ids / description
      Previous value: -"Ids from search results, in the order to show them."New value: +"Ids from search_contracts or search_grants results (not award ids), in the order to show them."
    • changedInput schema / properties / ids / items / description
      Previous value: -"The id field of a search result."New value: +"An opportunity's id from a search result (the tool says which searches); not an award id (search_awards, get_company)."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior the annotations don't: a hard cap of 10 ids, best-first ordering, silent non-display of search_jobs ids and award ids, and the expectation that the agent's own reply stays a short summary because the card renders the rows. It stops short of saying whether out-of-scope ids are silently dropped or rejected, which is the one remaining ambiguity.

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?

Four short sentences, front-loaded with the action and its timing, then constraints, then exclusions. Every clause carries information an agent needs; there is no filler or repetition.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps: when to call it, which id sources are valid, how many, in what order, and how the agent's text reply should relate to the rendered card. It is complete for a one-parameter presentation tool.

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 defines the single ids parameter, its source searches, the exclusion of award ids, the 1-10 bounds, and the ordering semantics. The description restates the same constraints rather than adding new meaning beyond them, so the baseline of 3 applies.

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 action and resource: display the opportunities the agent picked as a card. It also explicitly separates this from searching (search_contracts, search_grants) and from fetching one result's details (get_opportunity), so an agent can route 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 explicit sequencing ("Use this last, after searching"), an explicit exclusion ("Do not use to search ... or for one result's details"), and names the alternative tool for each excluded case. Nothing about when to reach for it is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.