Skip to main content
Glama
WYRE-AI

gorelo-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gorelo_list_tickets

Read-only

List and filter service provider tickets by status, priority, client, tags, type, group, assignee, and dates; page results with cursor pagination and updatedOn/createdOn sorting.

Instructions

Lists tickets for the service provider using cursor pagination. Default sort is updatedOn desc.

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword matched against the ticket title, number and display number. Up to 200 characters.
cursorNoOpaque pagination cursor from a previous page; omit for the first page.
sortByNoSort field: updatedOn (default) or createdOn.
tagIdsNotag ids; a ticket matches if it carries any of them.
typeIdsNoticket type ids to include.
groupIdsNogroup ids; a ticket matches if it is subscribed to any of them.
pageSizeNoNumber of items per page. Clamped to 1–200 (default 50).
clientIdsNoclient ids to include. Omit for every client.
sortOrderNoSort direction: asc or desc (default).
statusIdsNostatus ids to include. Omit for every status.
contactIdsNocontact ids to include.
priorityIdsNopriority ids on the public scale — None=0, Urgent=1, High=2, Normal=3, Low=4.
createdSinceNoISO-8601 timestamp; keeps only tickets created at or after it.
updatedSinceNoISO-8601 timestamp; keeps only tickets updated at or after it.
createdBeforeNoISO-8601 timestamp; keeps only tickets created strictly before it.
updatedBeforeNoISO-8601 timestamp; keeps only tickets updated strictly before it.
leadAssigneeIdsNolead assignee ids to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv1.1.1
    • addedInput schema / properties / clientIds / description
      Added value: +"client ids to include. Omit for every client."
    • changedInput schema / properties / clientIds / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / contactIds / description
      Added value: +"contact ids to include."
    • changedInput schema / properties / contactIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / createdBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only tickets created strictly before it."
    • changedInput schema / properties / createdSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only tickets created at or after it."
    • changedInput schema / properties / groupIds / description
      Previous value: -"A ticket matches if it is subscribed to any of these groups."New value: +"group ids; a ticket matches if it is subscribed to any of them."
    • changedInput schema / properties / groupIds / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / leadAssigneeIds / description
      Added value: +"lead assignee ids to include."
    • changedInput schema / properties / leadAssigneeIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items per page, clamped 1-200 (default 50)."New value: +"Number of items per page. Clamped to 1–200 (default 50)."
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / priorityIds / description
      Previous value: -"None=0, Urgent=1, High=2, Normal=3, Low=4."New value: +"priority ids on the public scale — None=0, Urgent=1, High=2, Normal=3, Low=4."
    • changedInput schema / properties / priorityIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / query / description
      Previous value: -"Keyword matched against the ticket title, number and display number."New value: +"Keyword matched against the ticket title, number and display number. Up to 200 characters."
    • addedInput schema / properties / sortBy / description
      Added value: +"Sort field: updatedOn (default) or createdOn."
    • removedInput schema / properties / sortBy / enum
      Removed value: -[
-  "updatedOn",
-  "createdOn"
-]
    • addedInput schema / properties / sortOrder / description
      Added value: +"Sort direction: asc or desc (default)."
    • removedInput schema / properties / sortOrder / enum
      Removed value: -[
-  "asc",
-  "desc"
-]
    • addedInput schema / properties / statusIds / description
      Added value: +"status ids to include. Omit for every status."
    • changedInput schema / properties / statusIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / tagIds / description
      Previous value: -"A ticket matches if it carries any of these tags."New value: +"tag ids; a ticket matches if it carries any of them."
    • changedInput schema / properties / tagIds / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / typeIds / description
      Added value: +"ticket type ids to include."
    • changedInput schema / properties / typeIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / updatedBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only tickets updated strictly before it."
    • changedInput schema / properties / updatedSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only tickets updated at or after it."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description carries a lower burden. It adds cursor pagination behavior and the default sort order, but does not describe rate limits, permissions, response shape, or pagination termination behavior.

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?

The description is two short sentences, front-loads the core operation, and contains essentially no wasted wording. Its brevity is appropriate for a list endpoint whose parameters are fully documented in the schema.

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 17-parameter list tool with only a readOnly annotation and no output schema, the description is thin. The schema covers filter parameters well, but the description does not explain return values or how the paginated result is structured, leaving some contextual gaps.

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 17 parameters are already documented in the schema. The description only restates cursor pagination and the default sort, which are already covered by the cursor, sortBy, and sortOrder schema descriptions; it adds no further parameter semantics.

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 states a specific verb and resource: 'Lists tickets.' It also scopes the operation to the service provider. It does not explicitly distinguish this tool from siblings such as gorelo_get_ticket or other ticket-list-adjacent tools, so it misses the top score.

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

Usage Guidelines3/5

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

The description gives context that this is a paginated list operation and notes the default sort. However, it provides no explicit when-to-use guidance, no when-not-to-use conditions, and no alternatives such as gorelo_get_ticket for fetching a single ticket.

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

Deploy Server

Other Tools