Skip to main content
Glama

Lovie Company Formation

Get Channel Ledger

fundraising_get_channel_ledger
Read-only

Each investor's true last inbound and last outbound across every readable channel, who owes the next message, how fast each side replies, and which channel they have actually answered on. Use this rather than an email-only last touch: aging computed from one channel is wrong as soon as a second one exists. An investor who has never answered is reported as unknown, never defaulted to email. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyId": "<companyId>"
    },
    "name": "fundraising_get_channel_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
ledgersNo
latencyWindowDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the trailing "Read-only" adds nothing and is essentially a restatement. The genuinely additive behavior detail is the guarantee that a never-answered investor is reported as unknown rather than defaulted to email, plus the scope being "every readable channel" — useful, but thin beyond that (no pagination, latency, or empty-result behavior).

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?

What the ledger contains is front-loaded in the first sentence, with the usage rationale and the unknown-handling rule following in logical order. Four sentences, no filler; the closing "Read-only." is the only redundant element given the annotations.

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 an output schema present, the description need not document return fields, and it correctly spends its words on what the ledger measures and how gaps are represented. It is nearly complete for a read-only single-parameter query; only the company-scoping of the result set is left implicit.

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% and the single required parameter is a companyId UUID wrapper, so the schema already carries the semantics. The description never mentions companyId or the scoping to one company, meaning it adds no parameter meaning beyond structured data — baseline 3 applies.

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?

The description names a concrete resource (per-investor channel ledger) and enumerates exactly what it contains: last inbound, last outbound, next-message owner, reply speed, and answered-on channel. It distinguishes itself from the email-only last-touch approach, though it does not name a specific sibling tool such as fundraising_get_list_touches, so routing is by concept rather than by name.

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?

"Use this rather than an email-only last touch" gives an explicit selection rule plus the reason (aging computed from one channel is wrong as soon as a second exists). It also states a data-handling exclusion — never-answered investors are unknown, not defaulted to email — but offers no guidance on when this tool is the wrong choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.