Skip to main content
Glama

Messages and reports

contact
Idempotent

action: message (a question, support, privacy request), cooperation (partners, media, creators), issue (wrong price, variant, category, shop), illegal (report illegal content, DSA).

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": {
      "action": "<action>"
    },
    "name": "contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoissue: price, variant, category, shop, other; cooperation: partner, media, creator
nameNoSender name
emailNoSender e-mail
topicNogeneral, support, cooperation, privacy (message)
actionYesOperation to run; help {topic:"contact"} lists each one's arguments
localeNoLanguage, e.g. cs
messageNoMessage
offer_idNoOffer id (issue)
page_urlNoPage address (issue, illegal)
shop_slugNoShop slug (issue)
good_faithNoReporter states good faith (illegal)
explanationNoWhy the content is illegal (illegal)
content_kindNoreview, product_info, offer, image, other (illegal)
organizationNoOrganization (cooperation)
product_slugNoProduct slug (issue, illegal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"contact\"} lists each one's arguments"
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive write of bounded scope, so the safety profile is covered. The description adds the action taxonomy, including that 'illegal' covers DSA reporting, which is useful domain context. It says nothing about what happens after submission — whether it is emailed, whether a ticket is created, or what confirmation the caller receives — so the post-call behavior remains opaque.

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

Conciseness4/5

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

A single compact sentence keyed on 'action:' that front-loads the routing decision and enumerates all four branches without padding. The telegraphic style and parenthetical fragments are efficient rather than wasteful, though they read as notes rather than prose.

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 15-parameter submission tool with no output schema, the description covers action selection but leaves the per-action field requirements implicit and says nothing about the return value or what the caller should expect after a successful submit. It is adequate to start the call, but an agent would still need the schema (and the referenced help call) to complete it confidently.

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 every parameter already carries its own meaning and the schema's action field even points to help {topic:"contact"} for per-action argument lists. The description adds value by tying actions to real-world categories, which helps an agent choose the action that gates the other 14 parameters. It does not, however, explain conditional requirements per action beyond what the schema already states.

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 defines the tool's four action categories — message, cooperation, issue, illegal — with concrete examples for each ('wrong price, variant, category, shop', 'report illegal content, DSA'). An agent can determine this is the platform's contact/report submission tool and pick the right category. The overall verb (submitting a message or report) is implied by the action list rather than stated 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?

Each action is annotated with the situation that selects it, which is effectively when-to-use routing guidance: a question or privacy request goes to 'message', partner/media inquiries to 'cooperation', data errors to 'issue', and illegal content to 'illegal'. What is missing is any exclusion or reference to an alternative tool (e.g., help or my_account siblings) for cases that don't fit these buckets.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources