Skip to main content
Glama

Lovie Company Formation

Refresh Pool Investor

fundraising_refresh_pool_investor

Research a relationship's investor again, at the member's request: this company's investor-research run starts now and writes a new brief and partner profile, which update the shared profile once the research package passes its checks. Call it only when the member asks for a refresh; a profile's age alone is never a reason. started is false only while the company's agents are paused.

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>"
    },
    "name": "fundraising_refresh_pool_investor"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdNoUUID value wrapper.
relationshipIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
startedNo

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.4/5.0
Behavior5/5

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

Annotations only declare openWorldHint=false and destructiveHint=false, so the description carries the important load: the call kicks off asynchronous background research, writes artifacts (brief, partner profile), and only touches the shared profile once a validation gate passes. The note that `started` is false only while agents are paused is exactly the kind of state semantics that annotations cannot express.

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 sentences, front-loaded with the action and its output, then the usage constraint, then the status-flag caveat. Every clause carries distinct information and nothing is padded.

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?

For a two-parameter tool with an output schema, the definition covers trigger conditions, async behavior, shared-state effects, and gating checks thoroughly. The notable remaining gap is concurrency/idempotency: it does not say what happens if a run is already in flight or if the call is issued twice, which matters for a costly research trigger.

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%, so both UUID-wrapped parameters are already documented, making baseline 3 appropriate. The description implies companyId through 'this company's investor-research run' but does not explain the companyId vs. relationshipId relationship or which one scopes the run, so it adds little beyond the 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?

States a specific verb and object ('Research a relationship's investor again') plus the concrete effects: a new investor-research run, a new brief and partner profile. This clearly separates it from read-only siblings such as fundraising_get_pool_investor or fundraising_get_relationship_pool_profile, which return existing data rather than triggering new work.

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?

Gives an explicit positive trigger ('only when the member asks for a refresh') and an explicit anti-trigger ('a profile's age alone is never a reason'), which is stronger than most definitions. It stops short of naming a concrete alternative to use when the member just wants to view an existing profile, so the agent must infer that from sibling names.

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.