alga-psa-mcp

Official

Overview Schema Source Related Servers Discussions Admin

alga_assets_list

Read-only

Browse and filter assets page by page by client, type, status, or location to review inventory; use text search separately to find assets by keyword.

Instructions

List assets, one page at a time. Use to browse or filter by client, type, status or location; use alga_assets_search to find assets by text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alga_assets_list"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`order`	No
`search`	No
`status`	No
`client_id`	No
`asset_type`	No
`location_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

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. The description adds the paging behavior ('one page at a time'), which is genuinely useful context, but says nothing about default page size, ordering, total counts, or how the filters compose.

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?

A single front-loaded sentence with a clarifying semicolon clause; nothing is padded. Slight compression cost: the guidance is packed tightly enough that the search-parameter tension is invisible.

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 an eight-parameter list tool with zero schema descriptions and no output schema, the description should explain ordering, page/limit behavior, and how its own 'search' param relates to alga_assets_search. It covers the browse-vs-search split but leaves half the parameters and the return shape opaque.

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 0%, so the description carries the burden; it names four filter concepts (client, type, status, location) that map to four of eight parameters. It adds no format or matching semantics, and leaves limit, page, order, and — most problematically — the 'search' parameter unexplained.

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 ('List assets') plus the pagination scope ('one page at a time'), then enumerates the filter dimensions and names the sibling it is not (alga_assets_search). An agent can pick it apart from the sibling search tool without opening either schema.

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?

Explicitly gives the use case ('browse or filter by client, type, status or location') and routes text lookup to alga_assets_search. The only ambiguity is that this tool also exposes a 'search' string parameter, which the description implicitly disclaims without addressing directly.

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

Deploy Server