VA Healthcare Facilities

get_facility_detail

Get detailed information for a specific VA facility.

Returns comprehensive facility data including address, contact info,
operating hours, services offered, patient wait times, and patient
satisfaction scores.

Args:
    facility_id: The VA facility ID (e.g., "vha_648", "vba_310",
        "nca_907"). Obtain from find_va_facilities results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`facility_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden of disclosure. It describes the comprehensive return data and implies a read-only operation. It does not mention error handling or permissions, but for a GET-style tool this is acceptable.

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?

The description is well-structured: a clear first sentence for purpose, a brief summary of response content, and an Args section. Every sentence contributes value without unnecessary verbosity.

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?

For a single-parameter tool with an output schema, the description covers the input source, what the output contains, and the workflow. It is self-sufficient and complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema offers no description (0% coverage), but the description compensates with a detailed Args section including example IDs (vha_648, vba_310, nca_907) and guidance to obtain the ID from find_va_facilities results. This fully defines the parameter semantics.

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?

The description clearly states 'Get detailed information for a specific VA facility' with a specific verb and resource. It lists concrete response categories (address, contact info, etc.), distinguishing it from sibling tools that find facilities or focus on services.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance to obtain the facility_id from find_va_facilities results, establishing the correct workflow. Does not mention when to avoid this tool or compare it to get_facility_services, so no exclusions are given.

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

All VA Healthcare Facilities tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: finding facilities, getting detailed info, and listing services. Even though get_facility_detail includes services, the tools are not confusing because one is comprehensive and the other is specific.

Naming Consistency4/5

All tools use a verb_noun pattern, but there is a minor inconsistency: 'find_va_facilities' uses plural 'facilities' while the other two use singular 'facility'. The verbs 'find' and 'get' are both clear, so the pattern is mostly consistent.

Tool Count4/5

Three tools is on the low end but appropriate for this focused read-only server. Each tool fills a necessary role—search, detail, and services—without unnecessary bloat.

Completeness4/5

The server covers the core read-only workflow: find facilities, view details, and check services. Minor gaps exist, such as no search by service type or listing all facilities without a location parameter, but these are not critical for the domain.

Resources

Need Help?