alga-psa-mcp

Official

Overview Schema Source Related Servers Discussions Admin

alga_tickets_search

Read-only

Search tickets by text and filter by client, status, priority, or assignee IDs. Closed tickets are omitted unless include_closed is true.

Instructions

Search tickets by text and return up to limit matches (not paginated). Closed tickets are left out unless include_closed is true. Narrow with comma-separated client, status, priority or assignee IDs.

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": {
      "query": "<query>"
    },
    "name": "alga_tickets_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes
`fields`	No	Comma-separated columns to search in.
`client_ids`	No	Comma-separated IDs.
`status_ids`	No	Comma-separated IDs.
`priority_ids`	No	Comma-separated IDs.
`include_closed`	No
`assigned_to_ids`	No	Comma-separated IDs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish the safe read-only profile, and the description adds real behavior: results are not paginated, capped at limit, and closed tickets are silently excluded unless include_closed is true. That default-exclusion rule is exactly the kind of invisible behavior an agent needs to avoid wrong conclusions.

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 purpose, then the default-exclusion caveat, then the narrowing options. Every clause carries information; no restatement of the title or padding.

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?

Covers the essentials for an 8-parameter search tool: match cap, non-pagination, closed-ticket default, and the comma-separated ID filters. Without an output schema, the description could still say what a match looks like or which columns are searched by default, but nothing critical for correct invocation is missing.

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 63%; the description adds meaning for include_closed (default exclusion) and limit (hard cap, no pagination), which the schema alone does not convey. It says nothing about query semantics (which columns are searched by default) or the fields parameter, so the remaining gap is not fully compensated.

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?

States a specific verb and resource ("Search tickets by text") plus the match cap, so the agent knows this is a text-search tool rather than a plain listing. It does not name or contrast with siblings like alga_tickets_list or alga_search, so differentiation is inferred rather than stated.

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?

Gives implied usage guidance: search by text, narrow with ID filters, and set include_closed to reach closed tickets. There is no explicit when-to-use-this-instead-of-alga_tickets_list or alga_search statement, leaving routing to the agent's inference.

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

Deploy Server