CompanyGraph

search

Find entities by words or by exact name. match: "text" (default) is a case-insensitive substring over name, tagline, fields, sections and table cells; match: "name" is the exact canonical name, across types. Optional type, owner (an id), limit, cursor. Returns results with id, title, type, matched, and page. A listing by type then name, not a ranking.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No
`limit`	No	Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
`match`	No
`owner`	No	An owner's id, to keep its entities
`query`	Yes
`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
`match`	Yes
`model`	Yes
`query`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties / cursor / description

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

addedInput schema / properties / limit / description

Added value: +"Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200."

Changed11 schema fields changedSep 21, 2026

addedInput schema / properties / cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / limit

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / match

Added value: +{
+  "enum": [
+    "text",
+    "name"
+  ],
+  "type": "string"
+}

addedInput schema / properties / owner

Added value: +{
+  "description": "An owner's id, to keep its entities",
+  "type": "string"
+}

addedInput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```
changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / match

Added value: +{
+  "enum": [
+    "text",
+    "name"
+  ],
+  "type": "string"
+}

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"
+}

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

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "matched": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "key": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "where": {
+              "enum": [
+                "name",
+                "tagline",
+                "field",
+                "section",
+                "table"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "where",
+            "key"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "owner": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tagline": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "type",
+      "owner",
+      "tagline",
+      "url",
+      "matched"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "model"
-]New value: +[
+  "query",
+  "match",
+  "results",
+  "page",
+  "model"
+]

First observedSep 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses the default match mode, the exact substring scope ('name, tagline, fields, sections and table cells'), case-insensitivity, the exact-name behavior, the response shape, and the non-ranking ordering.

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 dense but efficient: every sentence adds a distinct fact, the most important semantics are front-loaded, and the 'not a ranking' clarification is placed at the end without repeating schema details. No filler or tautology.

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 six-parameter tool with an output schema, the description covers defaults, matching semantics, optional parameters, pagination hints, and return fields. It is missing only the valid values or format for 'type' and explicit routing to sibling tools, which keeps it from a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, so the description must compensate, and it adds genuine meaning to the query and match parameters: the 'text' mode's search scope and the 'name' mode's canonical exactness. It even explains the return fields. The only notable gap is that 'type' is left without semantics or allowed values in both the schema and description.

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 ('Find') and resource ('entities'), and precisely distinguishes the two match modes: case-insensitive substring over named fields vs exact canonical name. It also notes the ordering ('by type then name, not a ranking'), which helps separate it from generic listing tools.

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?

The description clearly implies when to use it: when you need to find entities by words or by an exact name. However, it never names any sibling tool such as list_entities or get_entity, nor does it state when not to use it, leaving alternatives and exclusions to inference.

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?