Skip to main content
Glama
Sign In
friends-mcp

friends-mcp

by ourostack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

upsert_group

Link participants to a shared group and upgrade their relationship from strangers to acquaintances by upserting group context.

Instructions

Upsert shared-group participant context: link each participant to the group, promoting strangers to acquaintances.

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": {
      "groupExternalId": "<groupExternalId>",
      "participants": "<participants>"
    },
    "name": "upsert_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupExternalIdYesthe group's external id
participantsYesparticipants [{ provider, externalId, displayName? }]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the behavioral effect of 'promoting strangers to acquaintances,' which is a useful side-effect. However, it does not mention idempotency, potential destructive actions, permissions required, or rate limits. The 'upsert' term implies insert or update, but no explicit statement of safety.

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?

The description is a single concise sentence that front-loads the purpose and key behavior. It contains no redundant information; every word contributes to clarity. Ideal for quick parsing.

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?

The tool has no output schema, so the description should explain return values or confirmations. It does not. Additionally, it lacks details on error handling, default behavior for missing groups, or any side effects beyond relationship promotion. For a simple two-param tool, it covers basic purpose but misses operational completeness.

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 100%, so parameters are already described structurally. The description adds semantic value by clarifying that participants are 'linked' and that their relationship status is upgraded. This goes beyond the schema's basic definitions and helps the agent understand the tool's effect.

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?

The description clearly states 'Upsert shared-group participant context: link each participant to the group, promoting strangers to acquaintances.' The verb 'upsert' and resource 'shared-group participant context' are specific. However, 'promoting strangers to acquaintances' is slightly vague and could be more explicit about the behavior. It distinguishes from siblings like 'list_friends' or 'link_identity' by focusing on group participant management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, expected contexts, or when not to use it. Sibling tools exist (e.g., 'link_identity', 'record_interaction'), but no differentiation is provided. This leaves the AI agent unclear about selection criteria.

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