Skip to main content
Glama
Sign In
linklore

linklore

Official
by linklore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

send

Share selected footprints to an openbox for team visibility without altering the home base. Accepts single or batch IDs.

Instructions

send(id, openbox) — share a footprint to an openbox (visible to others). Both id and openbox are required.

  • send(id='lr-x'|'dc-x', openbox='ai-team') share one item

  • send(id=['lr-x','dc-y'], openbox='ai-team') a batch Not my-server backup — that's push. The home base is untouched — this copies into the openbox. Take down (inverse): rm(sent='lr-x'|'dc-x', openbox='ai-team') — sender only, home base untouched. (space= is an alias for openbox= — both work)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
helpNo
spaceNo
openboxNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the home base is untouched (copy), visible to others, supports batch, and aliasing. However, it does not mention permissions, rate limits, or error handling.

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?

The description is organized with a summary line, examples, contrasts, and alias note. It is slightly verbose but front-loads key info and uses bullet-point structure effectively.

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?

Given the absence of annotations and an output schema existing, the description adequately covers main use cases, batch mode, and inverse operation. It lacks details on output format and edge cases but is complete enough for typical usage.

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 0%, so description must compensate. It explains id (with format examples), openbox (with examples), and space as alias. The help parameter is left unexplained, but overall adds significant meaning beyond the 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?

The description states 'share a footprint to an openbox (visible to others)' with verb and resource clearly defined. It also distinguishes from sibling tools like push and rm.

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 provides explicit when-to-use context, contrasts with push for backup, and mentions the inverse rm command. It also gives concrete examples showing both single and batch usage.

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