RetailHardHat

List Diligence Tab

list_diligence_tab

Read-onlyIdempotent

Read diligence tab with your account's permissions. 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_diligence_tab"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already confirm the tool is read-only and safe. The description adds critical behavioral details regarding access ('with your account's permissions') and governance ('MCP approval requirements'), which are essential operational behaviors not covered by the hints.

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?

The description is brief and efficient. It front-loads the most important operational context (permissions and approval rules) immediately, ensuring high value density.

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?

Given the specific nature of the 'diligence tab' tool, providing the details about organizational permissions and required workflow approvals is a complete and necessary step for an agent to use this tool correctly within a business environment.

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?

Since the input schema is detailed, the description does not add specific technical meaning (e.g., data types or expected formats) beyond what the schema already provides. It fulfills the baseline requirement for tools with defined schemas.

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 clearly states the action ('Read diligence tab') and the general scope. It is strong but slightly elevated from a functional definition by including operational constraints, which slightly detract from a pure purpose statement.

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 description implies constraints by discussing 'MCP approval requirements' and that 'business workflow approvals always apply.' This gives context on when the tool operates but does not explicitly define its boundaries compared to alternatives.

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?