Skip to main content
Glama

Request integration

request_integration

Tells the backlane team that the user wants a marketplace that list_integrations does not offer yet. Only call it after checking list_integrations and after the user agreed to send the request. It does not connect anything.

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": {
      "marketplace_name": "<marketplace_name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "request_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: what the user wants to do with it (e.g. sync orders, list products) or other context from the user.
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
marketplace_nameYesThe marketplace as the user calls it, e.g. "bol.com" or "Amazon DE".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write; the description adds the meaningful behavioral caveat that it 'does not connect anything,' so the agent knows no integration is actually provisioned. It leaves out what the submission returns or how duplicate requests are handled, so it stops short of full disclosure.

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, front-loaded with the purpose, then the preconditions, then the side-effect clarification. No filler and no restatement of the title.

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 five-parameter write with no output schema, the definition covers purpose, gating, and the key side-effect boundary. The remaining gap is what happens after submission (confirmation, ticket identity, follow-up), which the agent might reasonably want to know.

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 five parameters including the heavily documented `context`, `llm_model`, and `conversation_id` are already explained in the schema. The description only implies that `marketplace_name` is the not-yet-offered marketplace; it adds no further parameter meaning beyond the structured fields.

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?

States a concrete verb and action (telling the backlane team that a marketplace is wanted) tied to a specific resource, and explicitly disambiguates from `list_integrations` by defining this as the gap-filling request path. An agent can distinguish it from the sibling without opening any schema.

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?

Gives two hard preconditions — call only after checking `list_integrations` and only after the user has agreed to send the request — and names the sibling to check. The when and the when-not are both explicit, leaving nothing 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.