Skip to main content
Glama
Aadi775
by Aadi775

unlink_artifact_from_session

Remove an artifact from a session to break its association, disconnecting the artifact from the session's context.

Instructions

Remove an artifact link from a session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artifact_idYesID of the artifact
session_idYesID of the session
actor_contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Without any annotations, the description fails to disclose behavioral traits such as whether the operation is reversible, if it has side effects, or requires specific permissions. It simply says 'remove', which is minimal for a mutation tool.

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 a single brief sentence (5 words) that is front-loaded and easy to parse, though it could include more information without losing conciseness.

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

Completeness2/5

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

Even though an output schema exists, the description does not explain what happens after removal (e.g., success confirmation, idempotency, or errors). A mutation tool like this needs more context for the AI agent to assess impact.

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?

The description adds no meaning beyond the schema's own parameter descriptions ('ID of the artifact' and 'ID of the session'). The third parameter 'actor_context' is undocumented in the schema and not mentioned in the description at all.

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 'Remove an artifact link from a session' clearly states the action (remove) and the resource (artifact link from a session), distinguishing it from sibling tools like 'link_artifact' and 'unlink_concept_from_session'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'delete_artifact' or 'close_session'. There is no mention of prerequisites, context, or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aadi775/MahoRAGa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server