Skip to main content
Glama
Sign In
INFATON MCP35

INFATON MCP35

Official
by infaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

delete_object

Set or clear a deletion flag on an object without permanent removal. Input object type, UUID, and optional unmark parameter.

Instructions

Установить/снять пометку удаления объекта. Физическое удаление НЕ выполняется.

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": {
      "full_name": "<full_name>",
      "guid": "<guid>"
    },
    "name": "delete_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYesUUID объекта
unmarkNotrue — снять пометку удаления (по умолчанию false — пометить)
full_nameYesТип объекта

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

In the absence of annotations, the description discloses a critical behavioral trait: it does not physically delete the object, only marks it. This is essential for an agent to avoid misinterpretation. However, it does not detail effects on object visibility or permission requirements.

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?

The description is extremely concise: two sentences that convey the entire purpose and key constraint. Every word is informative with no fluff.

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

Completeness3/5

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

For a simple boolean toggle, the description covers the core behavior but omits relevant context such as object existence requirements, error conditions, or how marked objects interact with other tools.

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?

All parameters have schema descriptions (100% coverage), so baseline is 3. The tool description adds no additional parameter-level information 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 clearly states the tool's purpose: setting or removing a deletion mark on an object, and explicitly notes that physical deletion is not performed. This distinguishes it from any hypothetical deletion tool and from siblings like update_object or set_attribute.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. It implies usage for marking/unmarking deletion, but no guidance on prerequisites or exclusions is provided.

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