Skip to main content
Glama

open_ticket

Opens a ticket with the JusticeLibre team ON BEHALF of the user (marked "via AI") to report wrong data, a missing source, a bug, or an idea. Meant for use only when the user asks for it or approves it. Permission tickets; AI limits on top of the user's own: 3 tickets a day, 5 messages an hour; 3 plain-text attachments at most. Replies are read with get_account_item. Requires a JusticeLibre account (OAuth sign-in); without one, the tool says so.

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": {
      "type": "<type>",
      "title": "<title>",
      "message": "<message>"
    },
    "name": "open_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYeserror (wrong data), missing (source or text missing), bug, idea.
titleYesPrecise title, 120 characters at most ("CT L1234-1: wrong renumbering date").
targetNoThe reference or URL concerned ("article:CT:L1234-1", a URL).
messageYesWhat is wrong, what is expected, the source. 4,000 characters at most.
attachmentsNoAt most 3, plain text only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the ticket is attributed to the user but marked 'via AI' (a reputational/attribution consequence), per-user rate limits (3 tickets/day, 5 messages/hour), attachment constraints, and the degraded path when no account exists. The annotations only say it is a non-idempotent, open-world, non-destructive write; the description supplies the operational and permission context the agent actually needs.

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?

Front-loads the action, then the permission gate, then limits and prerequisites, which is the right order for an agent deciding whether to call. It is dense and mostly earns its words, though the semicolon-chained limit clauses and the fragment 'Permission tickets;' read as slightly compressed notes rather than polished prose.

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?

Covers everything needed for a write tool: who the ticket is attributed to, the approval requirement, auth prerequisite and its failure mode, rate limits, and where the reply surfaces. An output schema exists, so the absence of return-value detail is not a gap.

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%, so the enum values, the 120-character title cap, the 4,000-character message cap and the plain-text attachment shape are already fully documented. The description restates the attachment and length limits without adding syntax, examples, or target-reference format guidance beyond what the schema carries, so the baseline of 3 applies.

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 (opens a ticket with the JusticeLibre team) plus the exact scope: on behalf of the user, marked 'via AI', for four enumerated report types. The closing note that replies are read with get_account_item separates it cleanly from reply_ticket and the read-side 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 an explicit gating condition ('only when the user asks for it or approves it') and a prerequisite (a JusticeLibre account via OAuth, with defined fallback behavior). It does not name reply_ticket as the alternative for continuing an existing thread, so the guidance is strong but not exhaustive.

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