Skip to main content
Glama

Lovie Company Formation

Approve Artifact

fundraising_approve_artifact

Marks an artifact approved so other agents may rely on it. Only call this when the member has said they approve this specific artifact.

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": {
      "artifactId": "<artifactId>"
    },
    "name": "fundraising_approve_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdNoUUID value wrapper.
artifactIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
artifactNo

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.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond them: approval is gated on explicit member consent and confers reliance rights to other agents. It does not say whether approval can be revoked, whether repeated calls are idempotent, or whether company scoping affects the approval.

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?

Two sentences, both load-bearing: the first defines the effect, the second defines the authorization gate. The consequence is front-loaded with no filler or hedging.

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 described, and the precondition plus effect cover what an agent must know before calling. The only gap is the optional companyId parameter and any note on whether approval is one-way, which matters for a pair of nested-object params.

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 the baseline is 3. 'This specific artifact' reinforces that artifactId is the required, single target, but the description adds nothing about the optional companyId wrapper or how the two identifiers must relate.

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 ('Marks an artifact approved') plus the downstream effect ('so other agents may rely on it'). The resource (artifact) implicitly separates it from siblings like approve_deck_version and approve_memo_version, though it never names an alternative explicitly.

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?

'Only call this when the member has said they approve this specific artifact' is a concrete, testable precondition that rules out speculative or batch approval. It gives clear when-to-call context but offers no explicit alternative for cases where that precondition is not met.

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.