StudiePoint AI

search_scholarships

Search StudiePoint's database of 300+ funded scholarships for African postgraduate students. Filter by destination country, field of study, minimum GPA (4.0 scale), degree level, and tier. Returns scholarship name, country, amount, deadline, minimum GPA, essay type, visa accessibility, and application URL.

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

Input Schema

Name	Required	Description
`tier`	No	'full_ride' = fully funded (tuition + living + flights). 'full_tuition' = tuition only, student funds living. 'affordable_eu' = low/no-tuition EU universities across 17 countries.
`field`	No	Field of study. Examples: 'engineering', 'medicine', 'business', 'law', 'sciences', 'arts', 'agriculture', 'public health', 'economics', 'computer science'.
`country`	No	Destination country. Examples: 'UK', 'Germany', 'USA', 'Canada', 'Australia', 'Netherlands', 'France', 'Japan', 'China', 'South Korea', 'Sweden', 'Norway'.
`min_gpa`	No	Maximum minimum GPA required (4.0 scale). Only return scholarships the student can qualify for.
`degree_level`	No	Degree level: 'masters' or 'phd'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the return payload (name, country, amount, deadline, minimum GPA, essay type, visa accessibility, URL), which is valuable given there is no output schema. It says nothing about result caps, pagination, sort order, or whether all filters are combined with AND, so key search behavior remains undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the scope and followed by the return shape, with no filler prose. The second half of sentence one partially duplicates the schema's parameter list, which is a minor redundancy rather than noise.

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?

For a read-only, zero-required-parameter search tool with a fully described schema, the definition covers scope, filters, and the return fields an agent needs to decide whether the results answer the user's question. The missing piece is filter-interaction behavior (AND semantics, empty-result handling) and any pointer to sibling tools for alternative paths.

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?

Schema description coverage is 100%, so every parameter including enum meanings for tier and degree_level is already documented in the schema; the baseline of 3 applies. The description's recital of the filter dimensions ('destination country, field of study, minimum GPA (4.0 scale), degree level, and tier') largely restates the schema rather than adding syntax, combination, or default-behavior guidance.

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?

Uses a specific verb+resource ('Search StudiePoint's database of 300+ funded scholarships') and scopes the audience ('African postgraduate students'), which an agent can distinguish from a generic lookup. It stops short of naming how it differs from the sibling match_scholarships, so an agent must infer that this is the filter-driven browse path rather than the personalized-match path.

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?

Usage is implied by the filter list ('Filter by destination country, field of study, minimum GPA...'), so an agent can infer this is the browse/filter tool. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to match_scholarships or get_scholarship, leaving the agent to guess which entry point applies.

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

All StudiePoint AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?