Signed

create_transaction

Record a transaction (cash flow) on a company: a buy (equity purchase or fund capital call), SAFE, sell, or distribution. Amounts are positive, in the company's currency unless you pass another. Target an existing company by slug, or pass a domain to find or create the company. Recording a transaction on a pipeline pitch converts it into a portfolio position.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	ISO 8601 date (YYYY-MM-DD). Defaults to today.
`name`	No	Name for a company created from domain. Defaults to a name derived from the domain. Ignored when the domain already matches one of your companies.
`type`	Yes	The cash-flow type. buy covers equity purchases and fund capital calls.
`amount`	Yes	Amount actually paid, positive. Direction comes from type, not sign.
`domain`	No	Alternative to company: the company's website domain. Matches your existing company by domain, or creates a new portfolio company from it.
`entity`	No	Investing entity id (from list_entities). Defaults to the entity the company was first transacted under, or your default entity.
`shares`	No	Shares bought or sold, for equity transactions.
`company`	No	Company or pitch to record on, by slug (from list_companies / list_pitches / search_companies).
`currency`	No	ISO 4217 code the amount, price, valuation and cap are in (EUR, GBP, CHF…), as the deal was done; don't convert. Defaults to the company's currency. On a company with no currency of its own and nothing recorded yet (no transactions, marks, metrics or round economics), this sets the company's currency; otherwise a transaction in another currency keeps its own.
`valuation_cap`	No	Valuation cap, for SAFEs. Also records a valuation mark on the company.
`price_per_share`	No	Price per share. Derived from amount / shares when omitted.
`post_money_valuation`	No	The round's post-money valuation, if known.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / amount / description

Previous value: -"Amount in USD, positive. Direction comes from type, not sign."New value: +"Amount actually paid, positive. Direction comes from type, not sign."

addedInput schema / properties / currency

Added value: +{
+  "description": "ISO 4217 code the amount, price, valuation and cap are in (EUR, GBP, CHF…), as the deal was done; don't convert. Defaults to the company's currency. On a company with no currency of its own and nothing recorded yet (no transactions, marks, metrics or round economics), this sets the company's currency; otherwise a transaction in another currency keeps its own.",
+  "type": "string"
+}

Changed2 schema fields changedOct 8, 2026

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

changedInput schema / properties / entity / description

Previous value: -"Investing entity id (from list_entities). Defaults to the entity the company was first transacted under."New value: +"Investing entity id (from list_entities). Defaults to the entity the company was first transacted under, or your default entity."

Changed1 schema field changedJul 30, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Name for a company created from domain. Defaults to a name derived from the domain. Ignored when the domain already matches one of your companies.",
+  "type": "string"
+}

First observedJul 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare the generic write/non-idempotent profile, but the description adds real side effects beyond that: a domain can create a new portfolio company, recording on a pitch converts it to a portfolio position, and passing a valuation_cap also records a valuation mark. It also clarifies that amounts are positive and direction is derived from type, which prevents sign errors.

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?

Four tightly packed sentences, front-loaded with purpose before the targeting rules and side effects. Nearly every clause adds information; the amount/currency phrasing slightly overlaps the schema descriptions but is not wasteful.

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 12-parameter mutation tool with no output schema, the description covers the critical semantics (targeting, sign convention, currency behavior, side effects). It does not describe what is returned (the created transaction/company), which would help, but coverage is otherwise strong given the rich schema.

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 100%, so the baseline is 3, but the description adds meaning over the schema for several key params: amounts are positive with direction coming from type, currency is the deal currency and should not be converted, and company/domain are alternative targeting mechanisms. Modest but genuine added value.

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?

Names a specific verb and resource ('Record a transaction (cash flow) on a company') and enumerates the exact transaction types (buy, SAFE, sell, distribution), with the buy subtype clarified as equity purchases and capital calls. This clearly distinguishes it from sibling creation tools like create_note and create_pitch.

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?

Gives concrete selection conditions: target an existing company by slug, or pass a domain to find-or-create. It also states a non-obvious consequence — recording on a pipeline pitch converts it into a portfolio position. However, it names no alternative tool or exclusion (e.g. when not to use vs. list_transactions), so it stops short of explicit when-not guidance.

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?