BridgesAgents

Abrir ocorrência do pedido

open_issue

Abre uma ocorrência de pós-venda no pedido, em nome do consumidor, depois que ficou pronto ou foi entregue (até 30 dias). kind: NOT_RECEIVED (não recebeu), WRONG_ITEM, DAMAGED, MISSING_ITEM, RETURN (quer devolver) ou OTHER. wants: REFUND, REPLACEMENT, RETURN ou OTHER. A loja responde em até 48 horas; acompanhe em order.issue do get_cart (status OPEN, ANSWERED com resolution e storeReply, RESOLVED, ESCALATED). Reembolso é feito pela loja, no checkout dela.

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

Input Schema

Name	Required	Description
`kind`	Yes	NOT_RECEIVED, WRONG_ITEM, DAMAGED, MISSING_ITEM, RETURN ou OTHER
`wants`	Yes	REFUND, REPLACEMENT, RETURN ou OTHER
`cartId`	Yes	id do carrinho (de create_cart)
`description`	Yes	O que aconteceu, nas palavras do consumidor (5 a 1000 caracteres)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the 48-hour store response SLA, the issue lifecycle (OPEN/ANSWERED/RESOLVED/ESCALATED) visible in get_cart, and the important boundary that refunds are settled by the store at its own checkout rather than by this tool. It does not address duplicate submissions or failure modes, and the non-idempotent nature is left to the annotation.

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?

Front-loads the action and eligibility, then enums, then follow-up mechanics. Every sentence carries information; nothing is padded.

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

Completeness5/5

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

There is no output schema, yet the description explains exactly where the result surfaces (order.issue in get_cart) and what statuses to expect, which is precisely what an agent needs to close the loop after calling.

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 coverage is 100% and the schema already lists the same `kind` and `wants` values, so the description mostly mirrors it, though the parenthetical glosses ('não recebeu', 'quer devolver') do add meaning. `cartId` and `description` are not elaborated beyond the schema.

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 specific verb and resource ('abre uma ocorrência de pós-venda no pedido, em nome do consumidor') plus the eligibility window (after ready/delivered, up to 30 days). This cleanly separates it from close_issue and the quote/adjustment siblings.

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 a clear precondition (order ready or delivered, within 30 days) and instructs which `kind` and `wants` values to pick for each situation. It does not explicitly name an alternative tool or state when not to open an issue (e.g. before delivery or after 30 days should go elsewhere), so it stops short of full routing guidance.

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

All BridgesAgents tools Inspect

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

Need Help?