Skip to main content
Glama

Agent Reliability

by dev.agentreliability

Get one Agent Reliability knowledge object

get_entity
Read-onlyIdempotent

Fetch one knowledge object by id, with its claims and the sources each claim cites. Use this once search, answer or get_topic has given you an id. An unknown id is not a dead end: the answer names near-miss ids you can retry with.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe knowledge object's id, as returned by search, answer, get_topic or get_related — the last segment of its canonical URL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
entityNo
recoveryNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"The knowledge object's id, as returned by search, answer, get_topic or get_related — the last segment of its canonical URL."
    • addedOutput schema / properties / entity / properties / media
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "alt": {
+        "type": "string"
+      },
+      "caption": {
+        "type": "string"
+      },
+      "credit": {
+        "type": "string"
+      },
+      "height": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "id": {
+        "type": "string"
+      },
+      "license_spdx": {
+        "type": "string"
+      },
+      "permissions": {
+        "additionalProperties": {
+          "type": "boolean"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "supports": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      },
+      "width": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id",
+      "url",
+      "alt",
+      "credit",
+      "license_spdx",
+      "permissions"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / entity / required
      Previous value: -[
-  "id",
-  "type",
-  "name",
-  "summary",
-  "tags",
-  "evidence_tier",
-  "confidence",
-  "last_verified",
-  "canonical_url",
-  "api_url",
-  "questions",
-  "claims"
-]New value: +[
+  "id",
+  "type",
+  "name",
+  "summary",
+  "tags",
+  "evidence_tier",
+  "confidence",
+  "last_verified",
+  "canonical_url",
+  "api_url",
+  "questions",
+  "claims",
+  "media"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / recovery
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "available": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "available_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "available_truncated": {
+      "type": "boolean"
+    },
+    "did_you_mean": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "next_tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "available_count",
+    "available",
+    "next_tool",
+    "hint"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds a useful behavioral trait: an unknown id is not a dead end, and the answer provides near-miss ids to retry. This exceeds what annotations convey.

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 sentences, front-loaded with the action, followed by a clear usage condition and a helpful edge-case note. No waste; every clause earns its place.

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?

The description tells the agent what the tool returns, when to call it, and how to recover from an unknown id. The output schema covers the return shape, so nothing critical is missing for a one-parameter read-only 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 the schema already explains the id parameter including how to obtain it and the canonical URL hint. The description merely says 'by id' and adds an error-recovery note for unknown ids, which adds little semantic detail beyond the schema.

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 opens with a specific verb and resource: 'Fetch one knowledge object by id', and names the payload ('with its claims and the sources each claim cites'). It also implicitly distinguishes from siblings by noting when it applies ('Use this once search, answer or get_topic has given you an id'), making it clear this is the targeted retrieval step.

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 description explicitly states when to use the tool: 'Use this once search, answer or get_topic has given you an id.' It gives clear context, though it doesn't explicitly list when not to use it or name a sibling alternative.

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

All Agent Reliability toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct retrieval mode: question answering, text search, entity fetch, topic browse, related traversal, source inspection, freshness, and corpus overview. The descriptions explicitly contrast overlapping pairs like answer vs search and get_topic vs search, so an agent can reliably choose.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and consistent for six of eight tools, while answer and search are plain verbs that still convey their action. This is a minor deviation rather than a mixed convention.

Tool Count5/5

Eight tools is well within the ideal range for a knowledge-corpus query server. Each tool covers a distinct retrieval need with no redundancy or bloat.

Completeness5/5

The read-side lifecycle is complete: discover via overview, search, answer, topic, and latest; drill in via entity and related; and verify via sources. The descriptions explicitly handle misses with near-miss ids and existing topics, so agents are not left at dead ends.

Resources