Skip to main content
Glama

Lovie Company Formation

Store Partner Profile

fundraising_store_partner_profile
Destructive

Store the full partner profile of a relationship's investor, the eight-chapter Strategic & Professional Profile: identity, coverage (Full, Substantial or Limited), the voice profile with source counts per channel, key quotes and the writing spec, 01 executive summary, 02 decision-making and communication (with the dimension / observed pattern / practical implication table), 03 what they look for, 05 background timeline, 06 person-attributed portfolio, 07 thesis with the questions the public record does not answer, and numbered sources that every cited text points at by source_id. Put the company's own 04 engagement strategy and fit hypothesis in company_profile: they stay with this company. The public part replaces the shared investor pool's copy, which every company reads, once the brief, evidence map, gate report and a PASS review are stored, identity.name is the relationship's investor, it carries nothing private, and members who may manage the raise stored the brief, the review and the profile; published_to_pool says whether it did, and pool_refusal says why not.

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": {
      "relationshipId": "<relationshipId>",
      "profile": "<profile>"
    },
    "name": "fundraising_store_partner_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
companyIdNoUUID value wrapper.
relationshipIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
artifactIdNo
poolRefusalNo
publishedToPoolNo

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

A3.5/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; the description earns credit for explaining what is actually destroyed or overwritten — 'The public part replaces the shared investor pool's copy, which every company reads' — and that company_profile content stays private to this company. It also flags the permission requirement for 'members who may manage the raise.' It stops short of saying whether a refused publication is an error or a silent partial write.

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 purpose is front-loaded, but the final sentence is an eighty-word run-on stringing together publication, replacement, identity validation, privacy, permissions, and the published_to_pool/pool_refusal outputs without punctuation or parallel structure. The chapter enumeration is long and mixes useful contract detail with paraphrasing of schema fields. Structure, not length alone, is the failure here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, yet the description still spends its closing clause describing published_to_pool and pool_refusal. For a 3-parameter, deeply nested, destructive write, the key gaps are failure behavior (what happens when the PASS review is missing, or when identity.name does not match the relationship's investor) and whether a re-store is an upsert or is rejected. Permission requirements are covered, which is the strongest part.

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 67% and the schema is deeply nested but structurally silent about intent, so the description adds real meaning: it assigns the investor-research chapters to profile.publicProfile and routes 'the company's own 04 engagement strategy and fit hypothesis' into companyProfile. That public/private split is not derivable from the schema alone. It says nothing about companyId or why relationshipId appears at both the top level and inside publicProfile, leaving those ambiguous.

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?

Opens with a specific verb and resource: 'Store the full partner profile of a relationship's investor,' and then enumerates the eight chapters that make up the payload, so an agent knows exactly what this writes versus the read-side siblings like fundraising_get_relationship_partner_profile. The purpose is unmistakable, though the sentence never explicitly names an alternative, so differentiation comes from the verb rather than a stated contrast.

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?

The description does convey a real precondition chain: the public part only replaces the pool's shared copy once 'the brief, evidence map, gate report and a PASS review are stored' and the acting member holds the right permissions. That is useful when-to-use context. However, it gives no guidance on choosing this over fundraising_set_voice_profile or fundraising_get_relationship_pool_profile, and never states what to do when the gate conditions fail, so usage is implied rather than explicit.

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.