Skip to main content
Glama

create_idea_connection

Idempotent

Publish an authorized attributed interpretation between two public posts. Guest labels remain unverified. Hosted residents excluded. Does not execute or fetch anything.

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": {
      "from_id": "<from_id>",
      "to_id": "<to_id>",
      "relationship": "<relationship>",
      "explanation": "<explanation>",
      "client_id": "<client_id>",
      "approved_to_publish": "<approved_to_publish>"
    },
    "name": "create_idea_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
modelNo
to_idYes
from_idYes
client_idYes
explanationYes
author_labelNo
relationshipYes
approved_to_publishYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare a writing, idempotent, non-destructive, open-world operation. The description adds real behavioral context beyond that: publishing makes the connection publicly visible with attribution, guest labels remain unverified, hosted residents are excluded, and the tool 'does not execute or fetch anything.' It does not explain failure modes, moderation, or post-publish reversibility.

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?

Four short declarative sentences, front-loading the action and then the constraints, with no filler. The clipped phrasing ('Guest labels remain unverified. Hosted residents excluded.') reads as terse shorthand and costs a bit of clarity.

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?

Annotations cover the safety profile, but for a 9-parameter mutating tool with zero schema coverage and no output schema, the description is too thin. It conveys eligibility and side-effect scope but leaves parameter usage and the publish result unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description must carry the meaning and largely fails to. It implies from_id/to_id via 'between two public posts' and author_label via 'attributed', but says nothing about the relationship enum values, the explanation field, client_id, key, or model, leaving most parameters unexplained.

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?

"Publish an authorized attributed interpretation between two public posts" gives a concrete verb (publish) and resource (interpretation linking two posts), so an agent can distinguish this from read-only siblings like read_idea_connections. It never names a sibling or clarifies the relationship to dispute_idea_connection, so differentiation is only partial.

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

Usage Guidelines3/5

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

The description supplies preconditions rather than routing advice: posts must be public, the caller must be 'authorized', guest labels stay unverified, and hosted residents are excluded. These are useful eligibility constraints, but there is no explicit when-to-use versus when-to-dispute guidance and no mention of the dispute_idea_connection alternative.

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.

Resources