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
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
portfolio_overviewA

Omega Healthcare Investors' portfolio as disclosed in the latest 10-K (FY2025): total investments by property type, facility mix, geographic concentration, and the operators named in the concentration note. For a ranked list of operators use operator_concentration — this overview names only the two operators the FY2025 filing discloses.

operator_concentrationA

Omega's operators ranked by share of total investments. Returns two separately-dated blocks that must not be blended: (1) fy2025Disclosed — the current filing's named concentrations (Maplewood ≥10% of investments, CommuniCare 7.2%; largest-by-revenue vs largest-by-investment differ); (2) fy2020FullRanking — the last complete per-operator table Omega ever filed (Dec 31, 2020), with lease vs mortgage decomposition and computed percentages. Use this for any 'top N operators' question and always report each block's as-of date.

resolve_operatorA

Resolve a free-text operator name to the curated Omega operator record and its CMS chain mapping (method, confidence, caveats). Use to disambiguate names or check whether CMS metrics are even possible for an operator before asking for them. Other tools resolve names internally, so calling this first is optional.

operator_facilitiesA

The CMS-certified nursing facilities affiliated with an operator (via its CMS chain), each with star rating, staffing hours, beds and occupancy, plus an aggregate summary. Output is paged (default 25 rows) — the summary block always covers ALL matching facilities. Accepts free-text operator names.

operator_metricsA

Deterministic CMS metrics for one or more operators (1–10, free-text names): average star rating with per-star distribution, share of facilities below the national average on reported nurse staffing hours per resident day, bed-weighted occupancy, and two-year constant-panel trends (Jul 2024 → Jul 2026) for star rating, staffing HPRD, and occupancy. When multiple operators are given, a server-computed pooled block (union of facilities, deduplicated) is included — do not sum per-operator numbers yourself. Operators without CMS coverage are reported as unsupported with the reason, never silently dropped.

portfolio_occupancyA

Best-supported occupancy estimate for Omega's portfolio. Omega's 10-K discloses neither occupancy nor a facility list, so this is a defined PROXY: bed-weighted occupancy (avg residents/day ÷ certified beds) across the US nursing facilities of Omega's mapped operator chains, with explicit coverage accounting (who is included, who is excluded and why, and what share of Omega's last fully-disclosed portfolio that covers). Low-confidence operator mappings are excluded unless includeLowConfidence is true.

find_facilityA

Look up individual CMS-certified nursing facilities by CCN (exact) or name fragment, optionally filtered by state. Returns full current metrics, the two-year metric history per snapshot, and — when the facility's chain or legal name maps back to one of Omega's known operators — that affiliation (which indicates the operator relationship, NOT proof that Omega owns the building). Use for drill-downs like 'tell me about their Dayton facility'.

national_benchmarksA

National reference values computed from the current CMS Provider Information file: mean reported total nurse staffing HPRD, star-rating mean and distribution, and bed-weighted national occupancy — each with method and sample size. Use these to contextualize operator metrics.

data_coverageA

What this server knows, from where, as of when — and what it cannot know. Call this when asked about data freshness, reliability, methodology, or why an answer is qualified. Mirrored as MCP resource coverage://data-sources.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
data-coverageSame payload as the data_coverage tool, for clients that surface resources.

TDQS

A4.4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: resolving names, viewing portfolio overview, ranking operators, listing facilities, computing metrics, estimating occupancy, individual facility lookup, national benchmarks, and data coverage. Even the overlapping facility tools differ by entry point (operator vs. CCN/name).

Naming Consistency5/5

All tool names follow a consistent verb_noun or noun_noun pattern in lowercase snake_case (e.g., resolve_operator, portfolio_overview, find_facility, data_coverage). There is no mixing of conventions or vague verbs.

Tool Count5/5

With 9 tools, the server is well-scoped for its domain of analyzing Omega's portfolio and CMS facility metrics. Each tool addresses a specific need without redundancy or bloat, falling comfortably in the ideal range.

Completeness5/5

The tool surface covers the full analytical workflow: operator disambiguation, portfolio perspective, concentration rankings, facility-level data, aggregated metrics with trends, occupancy estimation, national context, and data transparency. No obvious gaps exist for the domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues