Skip to main content
Glama

MyAITwin

by com.lutolearn
OverviewDiscussionsAdmin

contribute_to_workspace

Copy one or more of your personal knowledge items into an organisation workspace. The originals stay in your personal twin unchanged — this creates copies in the workspace so all members can retrieve them. IMPORTANT: This is a sharing action. Always confirm the items and target workspace with the user before calling this with multiple items. Items you do not own, or that are already in the workspace, are reported as failed per-item rather than aborting the whole batch. If you belong to exactly one workspace you can omit workspace_id; otherwise call list_workspaces first to get the ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idsYesIDs of the personal knowledge items to contribute (from search_twin, list_recent, etc.)
workspace_idNoTarget workspace ID. Omit only if you belong to exactly one organisation workspace; otherwise look up IDs with list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Explains non-destructive nature (originals unchanged), creates copies, and per-item failure reporting. Annotations already indicate readOnlyHint=false but description adds critical behavioral details.

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?

Concise paragraph front-loading action, then important usage notes. No redundant sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all key aspects: action, preconditions (user confirmation), behavior for edge cases (ownership, duplicates), and workspace selection. No output schema needed given clear description.

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 has 100% coverage, so parameters are well-defined. Description adds value by explaining workspace_id omission rule and user confirmation need, beyond 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?

Description clearly states it copies personal knowledge items to a workspace, distinguishing from siblings like add_knowledge or delete_knowledge. Verb and resource are specific.

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?

Provides explicit guidance: confirm with user for multiple items, workspace_id omission rule, and per-item failure handling. Also references list_workspaces for ID lookup when needed.

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

All MyAITwin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources