Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

attach_skill_to_agent

Assign a skill to an agent to enable its use. Verify the attachment using list_agent_skills before publishing, as the link is not visible in the agent entity.

Instructions

Scope a skill to a agent so the agent uses it. Verify it landed with list_agent_skills before request_publish_agent — the link lives outside the entity body, so re-reading the agent will not show it.

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": {
      "agentId": "<agentId>",
      "skillId": "<skillId>"
    },
    "name": "attach_skill_to_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYes
skillIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Discloses key behavioral trait: the link lives outside the entity body, so re-reading the agent won't show it. No annotations provided, but this is sufficient for the tool's simplicity.

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?

Two concise sentences, each essential. First sets purpose, second provides critical workflow guidance without unnecessary words.

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?

Covers purpose, verification step, and behavioral caveat. Missing parameter details, but given the simple inputs and lack of output schema, it is reasonably complete. Could mention it's a mutation.

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 coverage is 0%, but the description adds no meaning beyond parameter names (agentId, skillId). Does not explain format, source, or constraints.

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?

Clearly states the tool scopes a skill to an agent so the agent uses it. It distinguishes from siblings like detach_skill_from_agent and attach_skill_to_workflow by focusing on agent-skill linkage.

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?

Explicitly advises verifying with list_agent_skills before request_publish_agent and explains that re-reading the agent won't reflect the link, giving clear when-to-use and action sequence.

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