UAAR University MCP Server

check_hostel_availability

Read-onlyIdempotent

Check available hostel rooms at UAAR University. Filter results by hostel name or room type to find suitable accommodation.

Instructions

Check available hostel rooms. Filter by hostel name or room type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_hostel_availability"
  }
}

Input Schema

Name	Required	Description	Default
`hostel_name`	No
`room_type`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jan 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already provide strong behavioral hints (readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false). The description adds value by specifying the filtering capabilities (by hostel name or room type), which isn't covered by annotations. It doesn't contradict annotations—the 'check' action aligns with readOnlyHint=true.

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 two short sentences with zero waste. It's front-loaded with the core purpose ('Check available hostel rooms') followed by filtering details. Every word serves a clear function, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (2 optional parameters), rich annotations covering safety and behavior, and the presence of an output schema (which handles return values), the description is reasonably complete. It covers purpose and filtering, though it could benefit from mentioning that parameters are optional or providing example usage scenarios.

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

Parameters4/5

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

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description compensates by explaining what the parameters do ('Filter by hostel name or room type'), adding semantic meaning beyond the schema's titles. However, it doesn't detail format constraints or provide examples for the string parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Check available hostel rooms' specifies the verb (check) and resource (hostel rooms). It distinguishes from sibling tools like 'check_book_availability' by focusing on hostel rooms rather than books, though it doesn't explicitly contrast with other hostel-related tools like 'get_hostel_fees' or 'get_hostel_rules'.

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

Usage Guidelines3/5

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

The description provides implied usage guidance by mentioning filtering capabilities ('Filter by hostel name or room type'), which suggests when to use this tool for specific queries. However, it lacks explicit guidance on when to use this versus alternatives like 'get_hostel_fees' or 'get_hostel_rules', and doesn't mention prerequisites or exclusions.

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

Deploy Server