Skip to main content
Glama

Submit a service request

request_create
Idempotent

Submits a request to the Barmaan team for a catalog service (kind service, needs family), a custom service, or a software project. Contact name, e-mail and phone come from your profile (a phone number must be saved there). Files cannot be attached here; add them on the website. Call without confirm first for a preview, show it to the user, then again with confirm:true and the preview_token. Retrying the same call does not create a duplicate.

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": {
      "kind": "<kind>",
      "description": "<description>"
    },
    "name": "request_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
kindYes
titleNoProject or asset name.
familyNoRequired for kind service. See request_catalog_get.
confirmNoSet true only on the second call, after the user approved the preview.
detailsNoOnly keys listed in extra_fields of the family.
serviceNoService slug from request_catalog_get, or 'other' / omitted.
softwareNoRequired for kind software.
client_keyNoOptional idempotency key.
descriptionYes
preview_tokenNoThe preview_token returned by the first call (same input).
required_dateNo
contact_methodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), the description discloses that contact name, e-mail and phone are pulled from the profile and that a saved phone number is a prerequisite. It also reveals the two-phase preview/confirm gate and the file-attachment limitation, which are non-obvious behaviors an agent could not derive from the structured fields.

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?

Five tight sentences, front-loaded with what the tool creates, followed by the workflow, the file caveat and the retry rule. The only mild redundancy is the no-duplicate retry sentence, which restates idempotentHint, but it reinforces the preview flow rather than wasting space.

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 13-parameter, nested-object mutation with no output schema, the description covers the workflow, prerequisites, and side constraints well. It stops short of saying what the preview or the successful response contains (e.g., a request identifier), which an agent handling the confirm step would benefit from knowing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 62% schema description coverage across 13 parameters, the description adds real meaning for the highest-risk fields: it ties kind to family, explains confirm as second-call-only, and explains preview_token as the value returned by the first call with the same input. It says nothing about client_key, details/extra_fields, or the software sub-object fields, so a few parameters rely entirely on the schema.

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 opens with a specific verb and resource ('Submits a request to the Barmaan team') and enumerates the three accepted request shapes (catalog service, custom service, software project) with their kind values. It does not explicitly contrast itself with lookalike siblings such as request_quote or submit_export_inquiry, so an agent must infer the boundary from the kind enum rather than from stated differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It prescribes the exact call sequence: call without confirm for a preview, show it to the user, then call again with confirm:true and the preview_token. It also states a hard exclusion ('Files cannot be attached here; add them on the website') and a retry rule, leaving nothing about when and how to invoke it to inference.

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