Signed

list_companies

Read-onlyIdempotent

List the companies in the authenticated user's portfolio, alphabetically, with per-company position aggregates (invested, current value, realized, MOIC, DPI, implied runway). Filter by status, investment type, entity, custodian, and/or tag; filters combine. Amounts are in the user's home currency, given as currency.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Only companies carrying this tag, by name (see list_tags).
`page`	No	1-indexed page number (default 1).
`entity`	No	Only companies with a transaction made through this investing entity, by id (from list_entities).
`status`	No	Only positions with this status (active, at_risk, dissolved, exited, awaiting_wire).
`per_page`	No	Results per page (default 30, max 100).
`custodian`	No	Only companies with shares held at this custodian: carta, angellist, pulley, or other.
`investment_type`	No	Only positions of this type: equity (direct), fund_lp (an LP stake in a fund), or spv.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / custodian

Added value: +{
+  "description": "Only companies with shares held at this custodian: carta, angellist, pulley, or other.",
+  "enum": [
+    "carta",
+    "angellist",
+    "pulley",
+    "other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / entity

Added value: +{
+  "description": "Only companies with a transaction made through this investing entity, by id (from list_entities).",
+  "type": "integer"
+}

addedInput schema / properties / investment_type

Added value: +{
+  "description": "Only positions of this type: equity (direct), fund_lp (an LP stake in a fund), or spv.",
+  "enum": [
+    "equity",
+    "fund_lp",
+    "spv"
+  ],
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Only positions with this status (active, at_risk, dissolved, exited, awaiting_wire).",
+  "enum": [
+    "active",
+    "at_risk",
+    "dissolved",
+    "exited",
+    "awaiting_wire"
+  ],
+  "type": "string"
+}

First observedJul 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the bar is lower. The description adds real context beyond them: alphabetical ordering, the exact aggregate fields returned, and that multi-filter combinations intersect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: what it returns first, then filter/currency semantics. Dense but front-loaded, with no filler. It could be marginally tighter given the filter list is repeated from the schema.

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?

With no output schema, the description carries return-value burden and does so reasonably (aggregate fields, ordering, currency). Pagination defaults and max pages live in the schema, so the remaining omission is minor.

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%, including enum value explanations and cross-references to list_tags and list_entities, so the baseline of 3 applies. The description restates the filter set without adding format or resolution detail beyond 'filters combine'.

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?

States a specific verb and resource ('List the companies') plus a clear scope ('in the authenticated user's portfolio'), and even enumerates the aggregates returned. It never names the sibling it differs from (search_companies, get_company), but the portfolio scoping implicitly separates it from a general search.

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?

It documents which dimensions can be filtered and notes that 'filters combine' (AND semantics), which is genuine usage information. However, it gives no when-to-use guidance or routing against search_companies/get_company/list_entities, so the agent must infer the appropriate tool.

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

All Signed 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?