Skip to main content
Glama

Signed

by com.signed.mcp
OverviewDiscussionsAdmin

search_companies

Read-onlyIdempotent

Search the authenticated user's companies (portfolio and pipeline) by name, domain, or entity name. Takes the same filters as list_companies (status, investment_type, entity, custodian, tag) to narrow the hits; for a filter alone with no query, use list_companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query — matched against company name, domain, and entity name.
tagNoOnly companies carrying this tag, by name (see list_tags).
pageNo1-indexed page number (default 1).
entityNoOnly companies with a transaction made through this investing entity, by id (from list_entities).
statusNoOnly positions with this status (active, at_risk, dissolved, exited, awaiting_wire).
per_pageNoResults per page (default 30, max 100).
custodianNoOnly companies with shares held at this custodian: carta, angellist, pulley, or other.
investment_typeNoOnly positions of this type: equity (direct), fund_lp (an LP stake in a fund), or spv.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Only companies carrying this tag, by name (see list_tags).",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful scoping fact that results are limited to the authenticated user's portfolio and pipeline, but says nothing about result size, pagination behavior, or matching semantics.

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, zero padding, and the core purpose is front-loaded before the routing advice. Every clause carries load — the corpus scope, the searchable fields, the filter parity, and the fallback tool.

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 an 8-parameter list/search tool with no output schema, the description covers purpose, scope, routing, and filter parity, and the schema carries all parameter detail. It stops short of describing what a hit looks like or result limits, which would help since no output schema exists.

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%, so every parameter (q, tag, entity, status, custodian, investment_type, page, per_page) is already documented in the schema. The description only notes that the filter set mirrors list_companies, which adds a cross-reference but no syntax or semantics beyond the schema; baseline 3 applies.

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 (search) and resource (the authenticated user's companies), and scopes the corpus explicitly as 'portfolio and pipeline'. It also names the fields searched (name, domain, entity name), so an agent can distinguish it from list_companies and search_investors without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: this tool is for a query, and 'for a filter alone with no query, use list_companies.' That is a concrete when-to-use-this vs when-to-use-the-alternative rule tied to a condition the agent can evaluate.

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

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