UAAR University MCP Server

list_scholarships

Read-onlyIdempotent

Find available scholarships at UAAR University. Filter by provider to locate funding opportunities for students.

Instructions

List available scholarships. Optionally filter by provider.

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": "list_scholarships"
  }
}

Input Schema

Name	Required	Description	Default
`provider`	No
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`total`	Yes
`offset`	Yes
`has_more`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jan 27, 2026

TDQS

B3.4/5.0

Behavior3/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), so the description doesn't need to repeat safety information. The description adds value by mentioning the optional filtering capability, but doesn't provide additional behavioral context like pagination behavior (implied by limit/offset parameters) or rate limits.

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 perfectly concise - a single sentence that states the core purpose upfront and includes the optional filtering capability. Every word serves a purpose with zero wasted text, making it easy for an AI agent 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 has comprehensive annotations covering safety and behavior, an output schema exists (so return values are documented elsewhere), and the tool's purpose is straightforward (list operation with filtering), the description provides adequate context. The main gap is the lack of explicit differentiation from sibling scholarship-related tools.

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

Parameters3/5

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

With 0% schema description coverage, the schema provides only parameter names and types without descriptions. The description mentions 'Optionally filter by provider' which explains the purpose of one parameter, but doesn't address the 'limit' and 'offset' parameters for pagination control. This provides some value but doesn't fully compensate for the schema coverage gap.

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 verb ('List') and resource ('available scholarships'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_scholarship_details' or 'check_scholarship_eligibility', which would require more specific differentiation.

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

Usage Guidelines2/5

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

The description provides minimal guidance with 'Optionally filter by provider' but doesn't explain when to use this tool versus alternatives like 'get_scholarship_details' for specific scholarship information or 'check_scholarship_eligibility' for eligibility assessment. No explicit when-not-to-use or prerequisite information is provided.

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

Deploy Server