universities
Server Details
Universities MCP — Hipolabs Universities API (free, no auth)
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-universities
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.3/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a clear and distinct purpose: searching for universities by name and/or country.
There is only one tool, so naming consistency is inherently perfect. The tool name 'search_universities' follows a clear verb_noun pattern, which is appropriate and consistent within this minimal set.
A single tool is too few for a server named 'universities', which suggests a broader domain. This minimal set lacks basic operations like retrieving details, creating, updating, or deleting university data, making it feel incomplete and thin for the apparent scope.
The tool set is severely incomplete for a universities domain. It only provides search functionality, missing essential CRUD operations such as get_university, create_university, update_university, or delete_university, which are necessary for full lifecycle coverage.
Available Tools
1 toolsearch_universitiesBInspect
Search for universities by name and/or country. Returns university names, countries, web pages, and domains. Both parameters are optional but at least one should be provided.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | University name or partial name (e.g., "Harvard", "MIT") | |
| country | No | Country name to filter by (e.g., "United States", "United Kingdom") |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns 'university names, countries, web pages, and domains', which adds value beyond the input schema. However, it lacks details on behavioral traits like rate limits, error handling, or pagination, leaving significant gaps for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded: it starts with the core purpose, followed by return details and parameter guidance in two efficient sentences. Every sentence earns its place without redundancy, making it concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (search with optional parameters), no annotations, and no output schema, the description is partially complete. It covers the purpose and return values but lacks details on output format, error cases, or behavioral constraints, making it adequate but with clear gaps for agent invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, providing clear details for both parameters. The description adds minimal value beyond the schema by reiterating that parameters are optional and at least one should be provided, but doesn't explain semantics like format constraints or interactions. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search for universities by name and/or country' specifies both the verb (search) and resource (universities). It distinguishes the search functionality by mentioning filtering criteria. However, without sibling tools, we cannot assess differentiation from alternatives, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides implied usage guidance: 'Both parameters are optional but at least one should be provided' indicates when to use parameters. However, it lacks explicit guidance on when to use this tool versus alternatives (no siblings mentioned) or any contextual prerequisites, making it adequate but with clear gaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!