Skip to main content
Glama

Lovie Company Formation

Get Insider Brief

fundraising_get_insider_brief
Read-only

The preparation for the question every lead candidate asks: which existing investors are following on, what may be said about each, a rehearsed answer with facts marked apart from framing, and the investors the answer cannot speak for. An investor with no recorded disclosure scope contributes nothing to the answer and is named as a gap. You are given each investor's scope and never the agreed sentence itself — the words another firm permitted about themselves stay in the founder's console. Say what the scope allows in your own words, and never repeat a sentence you were not given. 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_insider_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
gapsNo
answerNo
disclosuresNo
participationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral context beyond them: investors with no recorded disclosure scope contribute nothing and are surfaced as gaps, and the agreed sentence itself is withheld so the agent must paraphrase only what the scope allows. That is meaningful guidance on output semantics and safe use that structured fields do not carry.

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

Conciseness2/5

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

The description is a dense, run-on, poetic paragraph rather than a front-loaded statement of action. The core instruction is buried mid-passage, and phrasing like 'the investors the answer cannot speak for' and 'facts marked apart from framing' costs length without sharpening invocation guidance.

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?

An output schema exists, so return values needn't be spelled out, yet the description still conveys the conceptual shape of the result (scopes, gaps, rehearsed answer) and the key constraint (never repeat an ungranted sentence). For a read-only tool with annotations and an output schema, this is essentially complete, with only the companyId-to-brief relationship 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% for the single companyId UUID param, so the schema already documents the input fully. The description adds no information about companyId or how it scopes the brief, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is framed as 'The preparation for the question every lead candidate asks' and describes the payload (investor scopes, gaps, a rehearsed answer with facts vs. framing). However, it never states a crisp verb+resource such as 'Get a briefing on which existing investors are following on,' so the actual operation must be inferred from narrative prose. It is distinguishable from siblings only by inference, not by an explicit statement.

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?

Usage is implied by the framing ('the question every lead candidate asks'), situating it in lead-investor diligence conversations. But there is no explicit when-to-use / when-not, and no sibling such as fundraising_get_briefing or fundraising_get_investor_intelligence is named as an alternative, leaving routing to inference.

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.