RetailHardHat

List Tasks

list_tasks

Read-onlyIdempotent

Use this when working with RetailHardHat tasks records in the connected organization. List tasks in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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_tasks"
  }
}

Input Schema

Name	Required	Description
`id`	No	Optional exact record UUID. Filters the authorized list to this record, without broadening permissions.
`limit`	No
`offset`	No
`search`	No
`siteId`	No	Optional RetailHardHat location UUID, not a location name. Resolve names with list_sites first.
`status`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by noting bounded pagination, search support, and approval caveats, though the approval note is somewhat vague for a list operation.

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?

The description is short and front-loads usage context, but the first two sentences overlap heavily by restating that this tool lists tasks in the organization. The approval sentence is generic and not clearly grounded in this read-only listing tool.

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?

The description covers organization scope, pagination, and search, and the output schema exists to explain return values. However, for a six-parameter list tool with multiple sibling task-listing tools, it omits clear differentiation and does not explain the status filter.

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

Parameters2/5

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

Schema description coverage is only 33%, with just id and siteId documented in the schema. The description mentions pagination and search at a high level, but it does not explain status, search semantics, or how the optional filters interact, leaving several parameters under-specified.

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 clear verb and resource: it lists task records in the connected organization. However, it does not distinguish this tool from closely related siblings such as list_project_tasks or list_task_children, so an agent must infer scope differences from the schemas.

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?

The phrase 'Use this when working with RetailHardHat tasks records' gives a broad usage context, and mentioning pagination/search implies exploration use. But there are no explicit when-not conditions or named alternatives for the several other task-listing tools.

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

All RetailHardHat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?