Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_french_companiesC

Search official French companies via DINUM/INSEE/INPI SIRENE/RNE Open Data API (15M+ entities: SIREN, SIRET, computed EU VAT, NAF code, revenue, labels, address & Pappers link).

search_eu_public_tendersA

Search active European Union public procurement tenders across 27 EU countries via official EU TED Search API v3 (returns title, buyer name, buyer email/phone/website, CPV codes, deadline & official URL).

search_clinical_trialsA

Search 500,000+ clinical studies via official U.S. NIH ClinicalTrials.gov REST API v2 (returns NCT ID, title, status, phases, lead sponsor, enrollment, central contact email/phone & study URL).

search_us_npi_providersA

Search 8,000,000+ U.S. physicians, dentists, clinics, hospitals & pharmacies via official U.S. CMS NPPES NPI Registry API v2.1 (returns NPI, specialty, practice phone/fax, address & authorized official).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a completely separate data domain (French company registry, EU TED tenders, NIH clinical trials, CMS NPI registry), so an agent can pick the right one from the entity type alone. There is no overlap in purpose or return shape between any two tools.

Naming Consistency5/5

All four tools follow an identical search_<domain_entity> snake_case pattern, with the geographic/domain qualifier consistently placed first. The pattern is fully predictable and readable.

Tool Count4/5

Four tools is lean but each maps to a distinct authoritative dataset, so none feels redundant. It is on the thin side for a multi-source open-data server, since there are no companion detail/lookup tools.

Completeness3/5

The surface is search-only: there is no get-by-identifier tool (e.g. fetch company by SIREN, tender by notice ID, provider by NPI) and no way to page through or expand results. Search covers each domain broadly, but agents hit a dead end when they need full record detail or follow-up retrieval.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues