Zooq

search_alumni

Read-onlyIdempotent

Alumni and current students of an institution (professional records + the education link). Page-paginated. Built for recruiting and warm-intro sourcing. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (>=1, default 1).
`sort`	No	Ordering. Accepted values: newest, oldest, recently_graduated.
`limit`	No	Results per page, 1-50 (default 20).
`degree`	No	Degree filter (min 3 chars), e.g. mba.
`geo_city`	No	City filter (min 3 chars).
`current_only`	No	Restrict to people currently studying there.
`end_year_max`	No	Latest graduation year.
`end_year_min`	No	Earliest graduation year.
`field_of_study`	No	Field-of-study filter (min 3 chars), e.g. computer science.
`start_year_max`	No	Latest enrollment year (>= start_year_min).
`start_year_min`	No	Earliest enrollment year (1900-current+10).
`normalized_name`	Yes	The institution's normalized name (lowercase, hyphenated). Discover it via search_schools — read data[].normalized_name.
`geo_country_code`	No	ISO country code filter, e.g. us.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No	Array in the example

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / normalized_name / description

Previous value: -"The institution's normalized name (lowercase, hyphenated). Discover it via /api/v1/search/schools — read data[].normalized_name."New value: +"The institution's normalized name (lowercase, hyphenated). Discover it via search_schools — read data[].normalized_name."

Changed1 schema field changedAug 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structural schema derived from a live example — field names and nesting only, no type constraints: fields may be absent, null, or a different primitive than the example, and new fields may appear. The text content block carries the same JSON.",
+  "properties": {
+    "items": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "education": {
+            "additionalProperties": true,
+            "properties": {
+              "degree": {
+                "description": "Example value was a string"
+              },
+              "end": {
+                "additionalProperties": true,
+                "properties": {
+                  "year": {
+                    "description": "Example value was a number"
+                  }
+                }
+              },
+              "field_of_study": {
+                "description": "Example value was a string"
+              },
+              "institution_id": {
+                "description": "Example value was a string"
+              },
+              "school_name": {
+                "description": "Example value was a string"
+              },
+              "start": {
+                "additionalProperties": true,
+                "properties": {
+                  "year": {
+                    "description": "Example value was a number"
+                  }
+                }
+              }
+            }
+          },
+          "first_name": {
+            "description": "Example value was a string"
+          },
+          "handle": {
+            "description": "Example value was a string"
+          },
+          "headline": {
+            "description": "Example value was a string"
+          },
+          "id": {
+            "description": "Example value was a string"
+          },
+          "last_name": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already convey read-only/idempotent/non-destructive behavior. The description adds useful behavioral context beyond annotations: results are page-paginated, each call costs 10 Zooq credits, and records are professional plus education-linked. No contradiction with annotations.

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?

Three short sentences, each carrying useful information: data scope, pagination, and use case/cost. It is efficient and front-loaded, though the phrase 'professional records + the education link' is slightly cryptic.

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 search tool with rich schema descriptions, an output schema, and safety annotations, the description adds the missing contextual pieces: pagination behavior, cost, and intended recruiting use. It is complete enough for an agent to invoke correctly, though it could name related tools.

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 the description does not need to repeat parameters. It adds only the generic 'page-paginated' hint, which is already implied by the page/limit parameters; no additional semantic value beyond the schema.

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 identifies the target data (alumni and current students of an institution) and the intent (recruiting and warm-intro sourcing), which makes the tool's purpose clear. It does not explicitly say 'search' or name sibling alternatives, so it lacks explicit differentiation from generic people-search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context: use this when sourcing alumni/current students for recruiting or warm intros. It does not state exclusions or point to alternatives such as search_people, so it falls short of full when-to-use/when-not-to-use guidance.

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

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