There's An AI For That

Get repository details

get_repository

Read-only

Get public details for one AI repository by its owner/repository slug or numeric ID. Preserve returned URLs exactly.

Input Schema

Name	Required	Description	Default
`id`	No	The numeric repository ID returned by search_repositories.
`slug`	No	The exact owner/repository slug returned by search_repositories.

Output Schema

Name	Required	Description	Default
`repository`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 13, 2026
- addedInput schema / oneOf
```
Added value: +[
+  {
+    "required": [
+      "slug"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  }
+]
```
- addedInput schema / properties / id
```
Added value: +{
+  "description": "The numeric repository ID returned by search_repositories.",
+  "minimum": 1,
+  "type": "integer"
+}
```
- changedInput schema / properties / slug / description
```
Previous value: -"The owner/repository slug returned by search_repositories."New value: +"The exact owner/repository slug returned by search_repositories."
```
- removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```
- changedOutput schema / properties / repository / properties / attributes / properties / company / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "object",
+  "null"
+]
```
- addedOutput schema / properties / repository / properties / attributes / properties / forks
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / github_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / homepage
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / language
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / owner
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / readme
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / related_models
```
Added value: +{
+  "items": {},
+  "type": [
+    "array",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / related_papers
```
Added value: +{
+  "items": {},
+  "type": [
+    "array",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / related_tools
```
Added value: +{
+  "items": {},
+  "type": [
+    "array",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / repository / properties / attributes / properties / repo_updated_at
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / repository / properties / attributes / properties / size_kb
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / repository / properties / attributes / properties / source_homepage
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / repository / properties / attributes / properties / source_primary_language
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / repository / properties / attributes / properties / source_pushed_at
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / repository / properties / attributes / properties / source_stars
```
Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / repository / properties / attributes / properties / source_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / stars
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / repository / properties / attributes / properties / tags
```
Removed value: -{
-  "items": {},
-  "type": [
-    "array",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / repository / properties / attributes / properties / topics
```
Added value: +{
+  "items": {},
+  "type": [
+    "array",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / repository / properties / attributes / properties / updated_at
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / repository / properties / attributes / properties / url
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
AddedSep 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: the scope restriction to *public* details and the non-obvious instruction to preserve returned URLs verbatim. Auth requirements and rate limits are not mentioned, keeping it short of a 5.

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 short sentences, zero filler, with the core purpose and the lookup keys front-loaded before the output caveat. Every clause earns its place.

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?

With an output schema present the return shape need not be described, and annotations cover safety, so the description's remaining job is scope and lookup semantics — both addressed ('public details', slug or ID). Missing only not-found/empty-result behavior for a lookup-by-key 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?

Schema coverage is 100% and both properties are already documented in the schema (including the oneOf requirement structure). The description restates the two lookup forms but adds no syntax, format, or precedence detail beyond what the schema provides, so the baseline of 3 applies.

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 ('Get public details for one AI repository') and names both lookup keys (owner/repository slug or numeric ID). It is clear it fetches a single entity, but it never names the sibling search_repositories as the bulk alternative, so differentiation is left implicit.

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?

No when-to-use, when-not-to-use, or alternative routing is given in the description itself; the only hint that search_repositories is the companion tool lives in the schema property descriptions. The 'Preserve returned URLs exactly' line is an output-handling instruction, not selection guidance.

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.