RealWorldAPIs

Get API

get_api

Read-onlyIdempotent

Retrieve one canonical API decision profile when you already know its name or slug. The response includes the full Verified/High capability profile with execution, access, approval, reversibility, physical-consequence and evidence fields. Exact slug or exact API name is preferred; a partial identifier is accepted only when it uniquely resolves to one record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "get_api"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes	Required API slug or API name. Exact matches are preferred; a unique case-insensitive partial slug/name match is accepted. If it is ambiguous or missing, use search_apis to find the exact identifier.

Output Schema

Name	Required	Description	Default
`name`	Yes
`record`	Yes
`source`	Yes
`evidence_policy`	Yes
`capability_graph`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 30, 2026

addedOutput schema / properties / capability_graph
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / record / properties / capability_profile

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / record / properties / capability_profile_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / record / properties / capability_summary

Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "record",
-  "source",
-  "evidence_policy"
-]New value: +[
+  "name",
+  "record",
+  "source",
+  "capability_graph",
+  "evidence_policy"
+]

Changed2 schema fields changedSep 27, 2026

changedInput schema / properties / identifier / description

Previous value: -"API slug or API name."New value: +"Required API slug or API name. Exact matches are preferred; a unique case-insensitive partial slug/name match is accepted. If it is ambiguous or missing, use search_apis to find the exact identifier."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "evidence_policy": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "record": {
+      "additionalProperties": true,
+      "properties": {
+        "a2a": {
+          "enum": [
+            "Yes",
+            "No",
+            "Unknown"
+          ],
+          "type": "string"
+        },
+        "agent_actionable": {
+          "type": "boolean"
+        },
+        "agent_capabilities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "agent_readiness_score": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "auth_methods": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "authentication_verified": {
+          "type": "boolean"
+        },
+        "capabilities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "category": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        },
+        "docs_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "llms_txt": {
+          "enum": [
+            "Yes",
+            "No",
+            "Unknown"
+          ],
+          "type": "string"
+        },
+        "mcp": {
+          "enum": [
+            "Yes",
+            "No",
+            "Unknown"
+          ],
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "openapi": {
+          "enum": [
+            "Yes",
+            "No",
+            "Unknown"
+          ],
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "public_documentation": {
+          "type": "boolean"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "website": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "x402": {
+          "enum": [
+            "Yes",
+            "No",
+            "Unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "record",
+    "source",
+    "evidence_policy"
+  ],
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so safety is covered. The description adds genuinely useful context beyond those hints: the response is the full Verified/High capability profile with named field groups, and the ambiguous-identifier failure mode is disclosed.

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 sentences, each earning its place: identity/scope first, response contents second, matching constraints last. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-identifier read tool with full annotation coverage and an output schema, this description supplies everything an agent needs: when to use it, what comes back, and how the identifier is resolved. No meaningful gap remains.

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 single parameter is already fully documented, including the exact-vs-partial matching rule and the guidance to fall back to search_apis. The description largely restates that matching rule rather than adding syntax or format detail, so the baseline 3 is correct.

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 (Retrieve) and resource (one canonical API decision profile) with a clear scope qualifier ('one canonical'). It is easily distinguished from search_apis and the other siblings, which are discovery-oriented rather than single-record retrieval.

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?

The opening clause 'when you already know its name or slug' tells the agent exactly the condition for choosing this over a search tool, and the partial-identifier rule sets the boundary further. It stops short of naming search_apis as the fallback in the description itself (that routing lives in the schema), so it's clear but not fully explicit about alternatives.

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

All RealWorldAPIs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.