Skip to main content
Glama
Sign In

Aimgod

by io.github.sendziuk
OverviewDiscussionsAdmin

Delete a focus point

delete_focus_point
DestructiveIdempotent

Delete a focus point for good. Only when the user clearly asks to delete 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": {
      "point_id": "<point_id>"
    },
    "name": "delete_focus_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
point_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable context beyond annotations: 'for good' emphasizes irreversibility, and 'Only when the user clearly asks' imposes a confirmation requirement. It still omits what happens to related data and error behavior.

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 short sentences, front-loaded with the core action and followed by a critical usage constraint. No wasted words.

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 destructive mutation with no output schema, annotations cover the safety profile (destructive, idempotent). The description adds permanence and confirmation guidance, but lacks details on cascading effects, failure modes, or how to identify the focus point. Adequate but with noticeable gaps.

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 description coverage is 0% for the single parameter point_id, and the description provides no information about it. The name is self-explanatory, but the description fails to compensate for the lack of schema documentation as required when coverage is low.

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 states a specific verb and resource ('Delete a focus point') and adds permanence ('for good'), making the action clear. It does not explicitly distinguish itself from siblings like update_focus_point or archive_sphere, but the delete operation is unambiguous.

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?

It provides a clear usage condition: 'Only when the user clearly asks to delete it.' This is a useful caution for a destructive tool. However, it does not name alternatives (e.g., update_focus_point for modifications) or explain when deletion is inappropriate beyond user intent.

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

All Aimgod toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources