Skip to main content
Glama
Lynsoft

fortimail-mcp-server

by Lynsoft

Delete GeoIP Profile

fortimail.profiles.geoip.delete
Destructive

Deletes a GeoIP profile by key in FortiMail, removing its geographic filtering rules from email security policies.

Instructions

Purpose: Delete GeoIP Profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesProfile mkey

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already carry destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond this – it does not disclose what gets removed, whether dependent references break, or what the response looks like. No contradiction exists, but no value is added.

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

Conciseness2/5

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

The text is short and front-loaded, but it is under-specified rather than concise – a bolded 'Purpose:' label wrapping a verbatim echo of the title earns no informational value.

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?

For a destructive delete operation with no output schema, the description should clarify irreversibility or prerequisites. Annotations partially cover safety, but the description leaves the agent without enough context to invoke confidently in a multi-sibling environment.

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?

There is a single parameter ('key') with full schema description coverage ('Profile mkey'). Per the baseline rule, complete schema coverage yields a 3, and the description adds no additional meaning about the key format or source.

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

Purpose2/5

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

The description merely restates the tool's title ('Delete GeoIP Profile') as its 'Purpose', adding no verb scope, target detail, or distinction from the many sibling delete tools (domains.delete, users.delete, queue.delete, etc.). An agent learns nothing beyond what the name already conveys.

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?

There is no guidance on when to use this tool versus alternatives, nor any precondition (e.g., that the profile must exist or be unreferenced). Deletion is irreversible per annotations, yet no caution or context is offered.

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