Skip to main content
Glama

Lovie Company Formation

Decide Proposal

fundraising_decide_proposal
Destructive

Approves, approves with an edit, or dismisses a proposal. Approval applies the change as the member deciding it, under that change's own permission; a refusal comes back on the proposal as FAILED with the reason, never silently. Only call this when the member has said, in their own words, that they approve or dismiss this specific proposal.

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": {
      "proposalId": "<proposalId>"
    },
    "name": "fundraising_decide_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
editedNo
reasonNo
decisionNo
companyIdNoUUID value wrapper.
proposalIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
proposalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / companyId
      Added value: +{
      +  "description": "UUID value wrapper.",
      +  "properties": {
      +    "value": {
      +      "format": "uuid",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, but the description adds valuable context: approval applies as the deciding member under that change's own permission, and refusals surface as FAILED with the reason rather than failing silently. That clarifies permission behavior and error handling beyond the annotations.

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?

The definition is three sentences and front-loads the operation before behavior and guardrails. Every sentence contributes useful information, though the permission/failure sentence is somewhat dense and could be split for readability.

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 shape is covered, and the description handles the main behavioral risks: destructive application, permission inheritance, explicit member consent, and failure visibility. The modest gap is that parameter semantics are thin for a five-parameter tool with nested UUID wrappers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% across five parameters. The description alludes to an edit and a reason, but does not explain the decision enum values, what the edited object should contain, or the role of companyId. It leaves most parameter meaning to an incomplete schema.

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?

The description uses three specific verbs (approves, approves with an edit, dismisses) against a specific resource (a proposal), making the operation unambiguous and easy to distinguish from sibling approval tools that target artifacts, decks, or memos.

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?

It gives explicit invocation criteria: only call when the member has stated in their own words that they approve or dismiss this specific proposal. That establishes both when to use and, implicitly, when not to use the tool. It does not name alternative tools, but the guardrail is clear and actionable.

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.