Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_party_website

Append one website or social media handle to a party without rewriting existing URLs. Uses a single atomic PUT to keep data consistent.

Instructions

Append a single website / social handle to a party. Atomic — one PUT to Capsule. Use this instead of update_party.websites for single-entry adds. The 'address' field is a URL when service='URL' or a handle (e.g. '@acmeco') for social services.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe website address. A URL when service='URL', or a handle (e.g. '@acmeco') for social services.
partyIdYes
serviceNoDefaults to 'URL' if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / required
      Previous value: -[
-  "address"
-]New value: +[
+  "partyId",
+  "address"
+]
  2. Addedv1.7.0
  3. Removedv1.6.2
  4. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only say the tool is not read-only and not destructive. The description adds meaningful behavioral context: 'Append' indicates it does not replace existing data, and 'Atomic — one PUT to Capsule' reveals the underlying operation's scope and side effect. It does not cover duplicate handling or authorization, but what it adds goes clearly beyond the minimal annotations.

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 carry a large amount of useful information with zero filler. The core action is front-loaded, followed by the atomicity detail and the routing instruction, and then the address semantics. Nothing is extraneous.

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 simple, single-resource append with a fallback to the schema for parameter details, the description covers action, scope, alternative, and parameter semantics. It does not mention the return value or error behavior, but the lack of an output schema makes a small gap. Overall, the information provided is sufficient for correct invocation.

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 67%, which already documents 'address' and 'service' in detail. The description restates the address semantics (URL vs. handle) but adds no new parameter-level information beyond what the schema provides. PartyId remains documented only by type, not by purpose.

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 a specific verb ('Append'), a clear resource ('a single website / social handle to a party'), and immediately distinguishes itself from update_party.websites. An agent can tell exactly what this tool does and how it differs from similar party-update tools.

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?

The description explicitly routes the agent: 'Use this instead of update_party.websites for single-entry adds.' This names the alternative and defines the exact condition that selects this tool, so no inference is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools