Skip to main content
Glama
taherkaraki

tie-mcp-server

by taherkaraki

delete_profile

Delete a profile instance by providing its unique ID. Use this tool to remove unwanted profiles from the system.

Instructions

Delete profile instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPath parameter: id
Behavior2/5

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

The description lacks details on behavioral traits such as permanence of deletion, required permissions, or side effects on associated data. With no annotations to compensate, the description fails to disclose critical safety information, though it does not contradict any annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one sentence, but this leads to under-specification. It is well-structured and front-loaded, but the brevity sacrifices necessary detail for safe usage. A longer description with context would improve quality.

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?

Given the low complexity (one parameter) and absence of output schema or annotations, the description should provide more context about the effect of deletion, reversibility, and how it differs from staging-related tools. Currently, it is insufficient for an AI agent to understand the tool's full behavior and safe invocation.

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 coverage is 100%, with the only parameter 'id' described as 'Path parameter: id'. The description adds no additional meaning beyond the schema, which is sufficient given full coverage. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete profile instance' clearly indicates the action (delete) and the resource (profile instance). It distinguishes from siblings like create_profile, update_profile by specifying deletion. However, it does not elaborate on what constitutes a 'profile instance' or differentiate from similarly named operations like unstage_profile, which could also result in removal.

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. The description does not mention prerequisites, when not to use, or suggest sibling tools like unstage_profile for non-permanent removal. This leaves the AI agent with no decision-making support.

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/taherkaraki/tie-mcp-server'

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