Skip to main content
Glama

List SwishrJobs capabilities

list_capabilities

List every task SwishrJobs can execute, with each one's inputs, deliverables, price, and whether it can run right now.

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": "list_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
paymentNo
serviceYes
versionNo
capabilitiesYes
execution_gateNo
execution_readyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose meaningful content beyond the name: the return payload includes price and live runnability ('whether it can run right now'). It does not state that the call is read-only/side-effect free, nor any auth or rate-limit considerations, which for a zero-annotation tool leaves a real gap.

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?

A single front-loaded sentence with zero waste; the returned-field enumeration is packed into the same clause rather than padded into a second paragraph.

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?

The tool is simple (no params) and an output schema exists, so return values need not be explained in prose. The description covers content and availability, but omits the workflow linkage to select_capability that would make the definition fully self-sufficient in a 37-tool namespace.

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 tool takes zero parameters, so the baseline is 4. Schema description coverage is irrelevant here and the description correctly adds nothing spurious about inputs.

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 names a specific verb ('List') and resource ('every task SwishrJobs can execute') and enumerates the returned fields (inputs, deliverables, price, availability). It is clearly distinguishable from the submit_* siblings, though it does not explicitly contrast itself with select_capability, the closest discovery-adjacent sibling.

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?

Usage is only implied: an agent can infer this is the catalog/discovery step that precedes select_capability and the submit_* tools, but the description never says when to call it, that it should be called first, or that select_capability is the follow-up. No exclusions or prerequisites are stated.

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