Skip to main content
Glama

search_universities

Search institutions, grading systems and institution candidates by name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_universities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results per source (default 10, max 50)
queryYesSearch text (at least 2 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about read-only behavior, result ordering, or the fact that results come from multiple heterogeneous sources. The only clue that output spans several sources is the schema's 'Maximum results per source' note, not the description. It also never explains what an 'institution candidate' is versus a real institution.

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?

A single front-loaded sentence with no filler, and the verb leads. The one weak spot is the unexplained term 'institution candidates', which costs a word budget without paying it back in meaning.

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

Completeness3/5

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

For a two-parameter, annotation-free, output-schema-free search tool the description is thinner than ideal: an agent cannot predict whether results are grouped per source, what fields come back, or how candidates differ from institutions. It is just adequate to know what to pass in, not what to expect out.

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 coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds only that the query matches names, implying code/id lookups are not supported, which is a marginal gain over the schema's 'Search text (at least 2 characters)'.

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?

A specific verb ('Search') plus the resources searched ('institutions, grading systems and institution candidates') and the key ('by name'). An agent can distinguish it from get_institution, which retrieves a single record rather than searching. The phrase 'institution candidates' is undefined and slightly muddies the otherwise clear scope.

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 gives no when-to-use guidance, no prerequisites, and never mentions the siblings it competes with (get_institution, resolve_grading_scale, list_countries). 'By name' hints at the query shape but not at when this tool is preferred over a direct lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.