CompanyGraph

find_evidence

Every edge into one skill, grouped by the type of the page that drew it. Use to check a claimed skill against its evidence. Input: skill, an id or canonical name; optional limit, cursor. Returns skill, evidence and page; a profile's claim arrives via Skills.Skill with its level, an evidence row via Evidence.Skill. Attributes are verbatim.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
`skill`	Yes	The skill's id or canonical name
`cursor`	No	`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`model`	Yes
`skill`	Yes
`evidence`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 21, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "nextCursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "returned": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "hasMore",
+    "nextCursor"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "skill",
-  "evidence",
-  "model"
-]New value: +[
+  "skill",
+  "evidence",
+  "page",
+  "model"
+]

Changed5 schema fields changedSep 21, 2026

changedInput schema / properties / skill / description

Previous value: -"The skill's canonical name"New value: +"The skill's id or canonical name"

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / evidence

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "attrs": {
+          "additionalProperties": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "id": {
+                    "type": "string"
+                  },
+                  "name": {
+                    "type": "string"
+                  },
+                  "type": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "type",
+                  "name"
+                ],
+                "type": "object"
+              }
+            ]
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "from": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "type",
+            "name"
+          ],
+          "type": "object"
+        },
+        "owner": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "stamp": {
+          "additionalProperties": {},
+          "properties": {
+            "end": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "kind": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "start": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "kind",
+            "start",
+            "end"
+          ],
+          "type": "object"
+        },
+        "to": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "type",
+            "name"
+          ],
+          "type": "object"
+        },
+        "via": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "from",
+        "via",
+        "to",
+        "attrs",
+        "owner"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / skill

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "tagline": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "type",
+    "name",
+    "tagline"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "model"
-]New value: +[
+  "skill",
+  "evidence",
+  "model"
+]

First observedSep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses aggregation/grouping behavior, the shape of results (skill, evidence, page), how profile claims vs evidence rows are represented, and that attributes are returned verbatim. This goes beyond the bare operation, though it doesn't address safety or side effects.

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?

The description is compact and front-loaded: purpose, use case, input, output, and data representation each earn their place in a short paragraph. There is no filler or repetition of schema details.

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?

For a tool with one required parameter, an output schema, and clear pagination semantics already documented in the schema, the description is sufficient. It covers the main use case, result shape, grouping behavior, and data-source semantics; the only minor gap is explaining what 'page' means beyond the output schema.

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 documents skill, limit, and cursor thoroughly, including clamping and cursor reuse. The description only restates that skill is an id or canonical name and that limit/cursor are optional, adding no meaning beyond the schema.

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?

The description states the operation in concrete terms: it returns every edge into one skill, grouped by the page type that drew the edge, and it frames the intended use ('check a claimed skill against its evidence'). This is specific enough to distinguish it from generic siblings like search or fetch, though the domain jargon ('edge', 'page') is not unpacked.

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?

It gives an explicit use case: 'Use to check a claimed skill against its evidence.' It does not name alternatives or exclusion conditions, so it stops short of a 5, but the guidance is clear enough for an agent to know when this tool is appropriate.

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

All CompanyGraph 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.

Resources

Need Help?