Skip to main content
Glama
Marcus-Chu-Chu

bahatanong

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_sqlA

Run one read-only SELECT over the BahaMap atlas (views: v_exposure, v_city_league, v_rainfall, data_dictionary). Row cap 200.

get_schemaA

List every queryable view, its columns, and their documented meanings.

search_briefsB

Semantic search over 1,710 bilingual public-safety briefs. lang: 'en' or 'tl'.

get_briefA

Fetch one barangay's brief by PSGC pcode. lang: 'en' or 'tl'.

glossary_lookupA

Define a methodology term (exposure_score, return_period, ...). Empty = list all.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a clearly distinct concern: run_sql executes queries, get_schema returns metadata, search_briefs finds briefs semantically, get_brief retrieves one brief by pcode, and glossary_lookup defines terms. There is no meaningful overlap between these operations.

Naming Consistency4/5

Four tools follow a verb_noun pattern: run_sql, get_schema, search_briefs, get_brief. glossary_lookup is the outlier, since it reads as noun_verb rather than lookup_glossary, but the naming is otherwise consistent and all use snake_case.

Tool Count5/5

Five tools is a well-scoped size for a domain combining queryable atlas views, brief retrieval/search, and glossary references. Each tool provides a distinct capability without redundancy or unnecessary surface area.

Completeness4/5

The core workflows are covered: schema discovery, data querying, brief search, brief retrieval, and term definition. A minor gap is that there is no direct way to enumerate all pcode values or list all briefs, though search_briefs and get_schema can help agents work around this.

Maintenance

ActivityMaintained
ResponsivenessNo issues