Skip to main content
Glama

AutoTasker Hub — China Social Data API

university_search

University directory (Hipolabs): name, country, web pages, domains. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
countryNoChina

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 burden. It does disclose a valuable trait the schema cannot convey — a $0.01 USDC cost — and lists the returned fields, but says nothing about matching behavior, result limits, auth requirements, or what happens with an empty result.

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 compact fragments, front-loaded with the resource and its data scope, with the price tag at the end. Nothing is redundant, though the telegraphic style costs a little readability.

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?

With no output schema and no annotations, the description does useful work by enumerating returned fields and pricing. It still leaves gaps for a 2-parameter lookup: the default country behavior and matching semantics are undisclosed, and there is no note on result size or pagination.

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 0%, so the description must compensate; naming 'name' and 'country' as scope indicators gives some signal about what the two parameters filter on. However, it never mentions that country silently defaults to China, nor whether matching is exact or substring, which is the single most consequential semantic detail here.

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 names the resource precisely ('University directory (Hipolabs)') and enumerates the returned data ('name, country, web pages, domains'), so an agent knows this is a university lookup rather than a generic web search. It does not explicitly contrast with sibling search tools like crossref_search or arxiv_search, keeping it short of a 5.

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?

There is no statement of when to use this tool versus the many other *_search siblings, and no prerequisites or exclusions are given. The agent must infer usage purely from the directory framing.

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.