Skip to main content
Glama

Lovie Company Formation

Set Fit Assessment

fundraising_set_fit_assessment

Record a relationship's fit on five dimensions: thesis_alignment, stage_fit, portfolio_precedent, active_deployment and partner_accessibility, each 0-100 with a one-line rationale and the URL of the source it rests on. A dimension you could not research is sent with not_researched true, never as a low score; it is left out of the composite. Give evidence_confidence and match_evidence (strong, moderate, adjacent, weak): the server computes the composite (weights 30/20/20/15/15), caps it by both, and places the tier. Replaces the previous assessment. Prefer proposing it with fundraising_propose_change (change kind SET_FIT_ASSESSMENT) so the founder approves it.

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>",
      "relationshipId": "<relationshipId>",
      "assessment": "<assessment>"
    },
    "name": "fundraising_set_fit_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNameNo
companyIdYesUUID value wrapper.
assessmentYes
relationshipIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
assessmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the sparse annotations (openWorldHint=false, destructiveHint=false) by disclosing that the server computes the composite with weights 30/20/20/15/15, caps it by evidence_confidence and match_evidence, and places the tier — and that not_researched dimensions are excluded from the composite. It also warns that the previous assessment is replaced, which is the key destructive-adjacent behavior an agent needs.

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?

Three front-loaded sentences, each carrying non-redundant information — dimension spec first, then the not_researched rule and server computation, then the replacement/approval guidance. Sentences are long and comma-heavy but every clause earns its place; 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?

Covers the scoring model, the missing-data rule, the server-side composite/tier computation, and the approval workflow, which is what an agent needs to call this correctly, and an output schema covers return values. It does not clarify the required companyId/relationshipId wrappers or which assessment subfields the caller must supply versus the server fills in, a small remaining gap.

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 only 50% and the schema is a large nested object, so the description carries real weight: it defines the dimensions array contents (score, rationale, source URL), the not_researched flag semantics, and the meaning of evidence_confidence and match_evidence. Many nested fields (pitchAngle, uncappedScore, citedSourceUrls, personalThesis) remain unexplained, keeping it short of a 5.

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?

Opens with a specific verb and resource: 'Record a relationship's fit on five dimensions', then names all five dimensions and their 0-100 scale. An agent can distinguish this from sibling writes like fundraising_update_relationship or fundraising_propose_change without opening the schema.

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?

Explicitly states the preferred path: 'Prefer proposing it with fundraising_propose_change (change kind SET_FIT_ASSESSMENT) so the founder approves it', and notes that this call 'Replaces the previous assessment'. That is a when-to-use, a when-to-prefer-alternative, and a side effect, all in one line.

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.