Skip to main content
Glama

aw.jobs.list

Read-only

Statuses for this session only, without selected audio or private URLs.

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": {
      "session": "<session>"
    },
    "name": "aw.jobs.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description does add genuinely non-obvious output context — that results are limited to the session and exclude selected audio and private URLs — which is valuable beyond annotations, though it says nothing about ordering, volume, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is good, but it is a noun-phrase fragment with no verb and its most important constraint (session scoping) is buried in a prepositional phrase. Brevity here reflects under-specification rather than efficient front-loading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing return values, and it only hints at them negatively by listing what is excluded. It never states what a 'status' entry contains, whether results are paginated or ordered, or what an empty result means — significant gaps for a listing tool.

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 100% and the single 'session' parameter is fully documented with a pattern and a strong warning not to log or publish it. The description adds no meaning about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Statuses for this session only' implies a session-scoped job listing, but it never states a verb or the resource being listed (jobs). An agent must infer from the name 'aw.jobs.list' that this enumerates jobs, and the description does not distinguish it from the sibling 'aw.status'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives, despite a sibling 'aw.status' that plausibly overlaps. The only scoping hint is 'for this session only', which constrains the query but does not tell an agent when to pick this tool over another.

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