tenderscope-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tendersA | Search open EU public tenders (TED, live). Returns cards: id, title, buyer, country, budget, currency, deadline, url. Only tenders with a future deadline are returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With a single tool there is nothing to confuse it with, so misselection is impossible. The tool's purpose (searching open EU tenders from TED) is narrow and explicit.
The lone name search_tenders follows a clean verb_noun snake_case pattern. There are no competing conventions to clash with.
One tool is thin even for a 'lite' server; the entire surface is a single search operation. It is defensible for a minimal read-only scope but leaves no room for detail retrieval or filtering.
Search is covered and returned cards include a url, but there is no get_tender detail lookup, no structured filters (country, CPV, budget range), and no pagination control. Agents can work around the gap via the url but the lifecycle is only partially covered.