Skip to main content
Glama

Offer a skill to a contact

skills_share

Offer one of your team's skills to one of your owner's contacts, or to a contact's agent. Confirm with your owner first. It reaches them as a request; nothing is installed until their owner accepts.

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": {
      "name": "<name>",
      "granteeType": "<granteeType>",
      "grantee": "<grantee>"
    },
    "name": "skills_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
nameYesSkill name ("deploy-checklist"), "workspace-slug/name" for one from outside your team, or its id
granteeYesperson: "@handle"; agent: "@workspace-slug/handle" or id
granteeTypeYesperson: a contact of your owner; agent: one of their agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already say this is a non-destructive, non-idempotent, open-world write; the description adds the crucial effect that nothing is actually installed until 'their owner accepts'. That tells the agent the call is a pending proposal rather than an immediate grant, plus the owner-confirmation requirement β€” exactly the behavioral context annotations can't carry.

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 short sentences: action and recipients first, prerequisite second, outcome third. Nothing is redundant and there is no filler.

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 four-parameter tool with no output schema, the description covers the action, the recipient kinds, the approval prerequisite, and the resulting state (a pending request). Minor gaps remain: nothing is said about what a repeat offer does given idempotentHint=false, or what a successful call returns.

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 100%: each of the four parameters, including the conditional 'as' and the dual grantee formats, is documented in the schema itself. The description's phrase 'or to a contact's agent' merely mirrors the granteeType enum, adding no format or edge-case detail beyond the schema. Baseline 3 applies.

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?

States a specific verb (offer/share) applied to a specific resource (one of your team's skills) with a bounded recipient set (owner's contacts or their agents). The scope is narrow enough to distinguish it from a general publish operation, so an agent can tell what it does without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear precondition β€” 'Confirm with your owner first' β€” which is real operational guidance for an agent deciding whether to call it now. It stops short of naming when to use an alternative (e.g., publishing to a wider audience instead of offering to a contact), so no explicit exclusions.

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