show_listShow one REACH list and a summary of its latest job.
Use this tool when you already know the list ID and need full metadata plus job status.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | Yes | Positive integer list ID (must be ≥ 1) |
| Name | Required | Description | Default |
|---|---|---|---|
| list | No | ||
| job_summary | No |
Changes observed during successful MCP inspections.
Output schema / properties / list / properties / expires_atAdded value: +{
+ "description": "ISO-8601 expiration timestamp",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / list / properties / is_expiredAdded value: +{
+ "type": [
+ "boolean",
+ "null"
+ ]
+}Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "job_summary": {
+ "properties": {
+ "latest_job_created_at": {
+ "description": "ISO-8601 creation timestamp",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "latest_job_finished_at": {
+ "description": "ISO-8601 completion timestamp",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "latest_job_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "latest_job_operation": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "latest_job_state": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "list": {
+ "properties": {
+ "created_at": {
+ "description": "ISO-8601 creation timestamp",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "file_ready": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "list_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "list_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "list_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "project_id": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "project_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "record_count": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "source": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=trueais, so the safety profile is covered. The description adds value by specifying the exact scope of the result – one list plus summary of latest job – which goes beyond the annotations. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with what it returns and when to use it. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, read-only, idempotent tool with an output schema, the description plus annotations fully cover what an agent needs to know. It states scope, return content, and selection condition.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema covers the single parameter with type, minimum, and a description that already conveys the list ID must be a positive integer. The description adds no extra semantics but none are needed at 100% coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Show') and resource ('one REACH list') plus what it returns ('summary of its latest job'). Distinguishes itself from sibling tools by requiring a known list ID and returning full metadata, which separates it from preview_list and list_lists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use the tool: when the list ID is already known and full metadata plus job status is needed. It doesn't name the alternatives it excludes (e.g., list_lists, job_status), but the context is clear enough for an agent to route to it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.