Skip to main content
Glama

There's An AI For That

by com.theresanaiforthat
OverviewDiscussionsAdmin

Get organization details

get_organization
Read-only

Get public details, papers, and linked paper authors and companies for one AI organization by slug. Preserve returned URLs exactly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe organization slug returned by search_organizations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / organization / properties / papers
      Added value: +{
+  "description": "Up to 50 most recent published papers linked to this organization.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "author_count": {
+        "type": "integer"
+      },
+      "co_organizations": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "integer"
+            },
+            "name": {
+              "type": "string"
+            },
+            "slug": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "slug",
+            "url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "date": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "slug": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "title",
+      "url",
+      "date",
+      "co_organizations",
+      "author_count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / organization / properties / papers_count
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / organization / properties / related_companies
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / organization / properties / related_models
      Added value: +{
+  "description": "Models directly linked to the organization when that relationship exists in the catalog.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / organization / properties / related_people
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / organization / required
      Previous value: -[
-  "id",
-  "entity_type",
-  "name",
-  "slug",
-  "canonical_url",
-  "url",
-  "description",
-  "attributes"
-]New value: +[
+  "id",
+  "entity_type",
+  "name",
+  "slug",
+  "canonical_url",
+  "url",
+  "description",
+  "attributes",
+  "papers_count",
+  "papers",
+  "related_people",
+  "related_companies",
+  "related_models"
+]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by scoping the data to 'public details' and warning to 'Preserve returned URLs exactly' when consuming the output.

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 no filler; the scope (one organization, by slug) is front-loaded and the URL-preservation caveat follows immediately.

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 explained, and the annotations cover safety. The only minor gap is the absence of any note on behavior for an unknown or invalid slug, which would be useful for a lookup tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the semantics. The description only repeats that lookup is 'by slug' and adds nothing about format or validation, so the baseline 3 applies.

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?

The description names a specific verb (Get) and resource (one AI organization by slug) and enumerates the payload (public details, papers, linked paper authors and companies), which distinguishes it from the sibling search_organizations and from get_company.

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?

Usage is only implied: identifying the key as a 'slug' for 'one' organization suggests a post-search lookup, and the schema notes the slug comes from search_organizations. There is no explicit statement of when to use this versus the search tool or when not to use it.

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 toolsInspect
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