Univs

Search education agencies

search_agencies

Read-onlyIdempotent

Search education agencies and study abroad consultants listed on Univs Agencies by name, office country or city, study destination and language. Returns public profile details (offices by city, destinations, languages, services, reviews) and the profile URL where students contact the agency. Neutral order; no contact details.

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_agencies"
  }
}

Input Schema

Name	Required	Description
`city`	No	Office city, e.g. "Tbilisi".
`page`	No	Result page (12 results per page).
`query`	No	Words in the agency name or profile, e.g. "medicine" or an agency name.
`language`	No	Language the agency speaks, e.g. "English".
`destination`	No	Study destination the agency helps with: country name or ISO code, e.g. "Georgia" or "GE".
`office_country`	No	Where the agency has an office: country name or ISO code, e.g. "India" or "IN". Comma-separate up to 5.

Output Schema

Name	Required	Description
`page`	No
`error`	No	Present only when the search failed.
`pages`	No
`query`	No	Filters that were applied.
`total`	No	Number of matching agencies.
`notice`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond annotations: results are public profiles with a profile URL, ordering is neutral, and contact details are omitted. It does not mention pagination or auth/rate constraints, but those are less critical for a read-only search.

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?

Three short sentences, front-loaded with the core search action and followed by return and ordering caveats. No filler or redundant restatement.

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 search tool with full schema coverage and an output schema, the description covers purpose, filter scope, return nature, ordering, and the contact-detail limitation. It leaves only explicit sibling routing and pagination behavior to inference or schema, so it is largely complete.

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 all six parameters, including page size, are fully documented in the schema. The description maps the search filters (name, country/city, destination, language) but adds little syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (education agencies and study abroad consultants), plus the filter dimensions. The entity is clearly distinct from sibling searches for institutes and programs, even though it does not explicitly name those alternatives.

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?

Explains the available filter dimensions but gives no explicit when-to-use guidance, prerequisites, or exclusions versus search_institutes, search_programs, or list_countries. Usage is implied by the resource name and filter list.

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

All Univs 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?