Skip to main content
Glama
iletimerkezi

iletiMerkezi MCP Server

Official

cancel_order

Cancel a future-scheduled SMS order before it is dispatched to the carrier. Only orders that have not started sending can be cancelled.

Instructions

The cancel-order endpoint cancels an order created via send-sms with a sendDateTime in the future, before it is dispatched to the carrier. Only orders that have not started sending can be cancelled; once the order enters the send pipeline, the cancel window has closed and the request returns 455.

Reference: https://www.iletimerkezi.com/en/docs/api/cancel-order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYes
Behavior4/5

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

Describes the constraint: only works before dispatch, returns error 455 if too late. No annotations, so description carries burden; it does well but lacks mention of side effects like order state change.

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 concise sentences plus a reference link. No wasted words, front-loaded with action and constraint.

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?

Covers main use and constraint but lacks return format, success indication, prerequisites. Reference link helps but does not fully compensate. Adequate for simple tool.

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?

Input schema has 1 parameter with 0% schema description coverage per context signals. The description adds no extra meaning beyond the schema defining the order ID. Baseline for low coverage is compensation, but not provided.

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 cancels a future-scheduled order created via send-sms, before it's dispatched. It distinguishes from siblings like send_sms.

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?

Explicitly says to use for orders with future sendDateTime that haven't started sending, and mentions the cancel window closes. No direct sibling comparison but clear condition for use.

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

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