Skip to main content
Glama
Sign In
alga-psa-mcp

alga-psa-mcp

Official
by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alga_tickets_get

Read-only

Retrieve a single Alga PSA ticket by ID to view its full details after a list or search.

Instructions

Get one ticket by ID. Use after a list or search to see full details.

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": {
      "id": "<id>"
    },
    "name": "alga_tickets_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds that this returns "full details" versus the summarized list view, which is real behavioral value, but it says nothing about failure behavior for an unknown/malformed ID or about access scoping.

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?

Two short sentences, front-loaded with what the tool does and followed by when to reach for it. Nothing is redundant or padded.

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?

This is a simple single-parameter getter with full annotation coverage and no output schema, so the bar is low, and the description covers purpose and workflow placement. It leaves the ID namespace ambiguous and never says what "full details" comprises, which is the main unresolved gap for an agent deciding between this and the external-link variant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter carries no schema description (0% coverage), so the description must carry the semantic load; "by ID" does identify the parameter's meaning as an identifier lookup. It does not clarify whether this is the internal ticket ID or an external-link identifier, which matters given the get_by_external_link sibling, and the pattern/format lives only in the schema.

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 ("Get one ticket by ID") and the singular "one ticket" contrasts with the list/search siblings. It does not explicitly distinguish itself from alga_tickets_get_by_external_link, so the differentiation is incomplete.

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?

"Use after a list or search to see full details" gives a concrete usage context and a workflow position relative to the list and search tools. It offers no exclusion rule for the alternate lookup path (get_by_external_link), which is the main remaining ambiguity.

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