Skip to main content
Glama

CompanyGraph

by io.companygraph
OverviewDiscussionsAdmin

list_entities

The entities of one type, by id. Use to browse a type; to find an entity by words or by name use search. Input: type, optional owner (an id) to keep one owner's entities, limit (default 50, at most 200) and cursor. Returns entities with id, type, name, tagline, owner, and page; follow page.nextCursor while page.hasMore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
limitNoEntries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
ownerNoAn owner's id, to keep its entities
cursorNo`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
typeYes
modelYes
entitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. Changed8 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / owner
      Added value: +{
+  "description": "An owner's id, to keep its entities",
+  "type": "string"
+}
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +false
    • addedOutput schema / properties / entities
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "owner": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tagline": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "name",
+      "tagline",
+      "owner"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • 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 / type
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "model"
-]New value: +[
+  "type",
+  "entities",
+  "page",
+  "model"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the returned fields, default and maximum limit, owner filtering, and the pagination contract via nextCursor and hasMore. This gives an agent enough behavioral context to call and iterate safely.

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, with the core purpose stated first, followed by usage routing and then input/output/pagination details. Every sentence adds value and nothing is redundant.

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?

Despite having no annotations, this description covers what the tool does, when to choose it over search, all inputs, the output shape, and the pagination loop. An agent has everything it needs to invoke the tool correctly and process the results.

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 75%, covering owner, limit, and cursor. The description mostly restates the schema's meaning for type and owner, but it adds useful context about limit's default and paging flow. Since the schema already documents most parameters, the baseline of 3 is appropriate.

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 uses a specific verb and resource: lists entities of one type for browsing, and explicitly contrasts itself with search for finding by words or name. This makes it easily distinguishable from the sibling tools without needing to open schemas.

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 clearly states when to use this tool ('Use to browse a type') and routes name/word-based lookups to search. It could more explicitly contrast with get_entity or list_types, but the browsing context and search alternative provide solid practical guidance.

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

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