Skip to main content
Glama

Lovie Company Formation

List Proposals

fundraising_get_list_proposals
Read-only

Lists proposals — open by default — grouped by relationship and ordered by what stalls if they sit. Check this before proposing: a second proposal about the same change is noise for the founder. 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_list_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo
pageSizeNo
companyIdYesUUID value wrapper.
pageTokenNo

Output Schema

NameRequiredDescriptionDefault
proposalsNo
totalCountNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the description earns credit for adding the default status filter and the ordering logic ('ordered by what stalls if they sit'), which the annotations do not cover. It stops short of describing pagination behavior or result shape.

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?

Three short clauses; the default and the grouping/ordering come first, the workflow guidance second, the read-only note last. No filler.

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 need not be explained, and the default filter plus ordering give the agent the context it needs to interpret results. Only pagination and the filter sub-parameters are 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 only 25% and four params carry enums/nested wrappers, so the schema is doing limited work. The description adds the implicit default for the statuses filter but says nothing about changeKinds, relationshipId, pageSize or pageToken — baseline 3 at best.

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 ('Lists proposals') plus the default scope ('open by default'), grouping and ordering. That is enough to separate it from proposal-writing siblings like fundraising_propose_change and fundraising_decide_proposal, though those siblings are not named.

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?

Gives an explicit pre-condition: 'Check this before proposing', and explains why — a duplicate proposal is noise for the founder. The agent knows exactly when in the workflow to call this.

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.