There's An AI For That

Search organizations

search_organizations

Read-only

Search and browse AI organizations. Exact names, short names, and derived acronyms rank first. Filter by type, country, or industry, and sort by paper count or latest activity.

Input Schema

Name	Required	Description	Default
`sort`	No		paper_count
`type`	No	Organization type to filter by (case-insensitive).
`limit`	No
`query`	No	Optional organization name, short name, acronym, domain, or description text.
`country`	No	Country name or country code to filter by.
`industry`	No	Industry name or slug to filter by.

Output Schema

Name	Required	Description	Default
`organizations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / type / description

Previous value: -"Organization type to filter by."New value: +"Organization type to filter by (case-insensitive)."

changedInput schema / properties / type / enum

Previous value: -[
-  "university",
-  "lab",
-  "institute",
-  "company"
-]New value: +[
+  "Educational",
+  "Nonprofit",
+  "Other",
+  "university",
+  "lab",
+  "institute",
+  "company"
+]

Changed13 schema fields changedOct 13, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Country name or country code to filter by.",
+  "type": "string"
+}

addedInput schema / properties / industry

Added value: +{
+  "description": "Industry name or slug to filter by.",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"AI organization name to search for."New value: +"Optional organization name, short name, acronym, domain, or description text."

addedInput schema / properties / sort

Added value: +{
+  "default": "paper_count",
+  "enum": [
+    "paper_count",
+    "latest_activity"
+  ],
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Organization type to filter by.",
+  "enum": [
+    "university",
+    "lab",
+    "institute",
+    "company"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[]

addedOutput schema / properties / organizations / items / properties / country
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / organizations / items / properties / industry
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / organizations / items / properties / latest_activity
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / organizations / items / properties / papers_count
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / organizations / items / properties / short_name
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / organizations / items / properties / type
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / organizations / items / required

Previous value: -[
-  "id",
-  "entity_type",
-  "name",
-  "slug",
-  "url"
-]New value: +[
+  "id",
+  "entity_type",
+  "name",
+  "slug",
+  "url",
+  "description",
+  "short_name",
+  "type",
+  "country",
+  "industry",
+  "papers_count",
+  "latest_activity"
+]

AddedSep 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context about ranking (exact names, short names, derived acronyms rank first), but says nothing about pagination or result limits 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero waste; the purpose and ranking behavior are front-loaded ahead of the filter/sort detail.

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?

An output schema exists, so return values need not be described, and the description covers the filter and sort surface. The main gap is the lack of sibling disambiguation, which matters given many adjacent search_* 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 coverage is 67% and the description names several parameters (type, country, industry, sort) plus sort values. It adds little beyond the schema and omits the query and limit parameters, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Search and browse AI organizations') with a clear scope. It does not, however, differentiate itself from siblings like search_companies or get_organization, which an agent must disambiguate on its own.

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?

The description implies usage by naming the available filters and sort options, but never states when to choose this over search_companies or get_organization, nor any exclusions or prerequisites.

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

All There's An AI For That 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.