Skip to main content
Glama
Sign In

Farrukh Inomov

by online.inomov
OverviewDiscussionsAdmin

Send Farrukh a message

send_message

Sends a message to Farrukh by email, e.g. a job offer or a project inquiry. He replies to the given address, usually within two working days. Confirm the content with the user first.

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": {
      "name": "<name>",
      "email": "<email>",
      "topic": "<topic>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage the message is written in: "de" or "en".en
nameYesFull name of the person writing
emailYesEmail address Farrukh replies to
topicYesjob: a job offer; freelance: a project; question: about a project or post; other
companyNoCompany, if any
messageYesThe message itself, 20 to 5000 characters

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only mark this as a non-read-only, open-world, non-idempotent write. The description adds genuinely new behavior: delivery is by email, the reply is routed to the supplied address, and turnaround is 'usually within two working days'. It also flags the confirm-before-sending human-in-the-loop step, which annotations cannot express.

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?

Three short sentences: what it does, expected response timing, and the confirmation prerequisite. Nothing is redundant and the core action is front-loaded.

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

Completeness4/5

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

For a six-parameter outbound-email tool with an output schema and full annotation coverage, the description supplies the essential missing context: channel, reply routing, latency expectation, and the confirmation step. Minor gaps such as delivery failure behavior or rate limits are not covered, but they are not critical for correct 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 description coverage is 100%, so all six parameters (including the topic and lang enums) are already documented in the schema. The description only adds the meaning of the email parameter ('He replies to the given address'), which is a marginal gain over the structured data. Baseline 3 applies.

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?

States a concrete verb and channel: 'Sends a message to Farrukh by email', with example use cases (job offer, project inquiry). It is unambiguous against the sibling set, which is otherwise read-only retrieval tools plus book_call, though it never names an alternative explicitly.

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?

Gives clear situational context ('a job offer or a project inquiry') and an operational instruction: 'Confirm the content with the user first.' It lacks explicit when-not guidance or a pointer to a sibling (e.g. book_call for scheduling a follow-up), so it stops short of a 5.

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

All Farrukh Inomov 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