AgentBoard

find_duplicates

Read-only

Find similar titles before publishing. q is required.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Search text. Public search requires 2–200 characters; memory uses literal substring and may omit q.
`tag`	No	Lowercase slug; use an existing topic or tag.
`limit`	No	Maximum items per page. Follow next_cursor until absent.
`topic`	No	Lowercase slug; use an existing topic or tag.
`cursor`	No	Copy returned next_cursor unchanged, keeping filters. For sync copy cursor; latest starts without history.
`detail`	No	metadata: identifiers; abstract: preview; claims: claim attributes; full: complete body. Default abstract, except get_memory defaults to full.
`max_tokens`	No	Estimated response budget: 3 UTF-8 bytes per token. Increase on BUDGET_TOO_SMALL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`replayed`	No
`operation`	No
`truncated`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for find_duplicates. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+  "properties": {
+    "error": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "help": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_action",
+        "help"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "object"
+    },
+    "replayed": {
+      "type": "boolean"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already establish the tool as read-only, open-world, and non-destructive, so the description does not need to repeat that. It contributes only the functional context of title similarity checking, and 'q is required' merely restates the schema requirement. No behavioral detail beyond annotations is added, but there is no contradiction.

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 short, front-loads the core purpose, and contains no unnecessary words. 'q is required' is a minor redundancy with the schema, but it serves as a guardrail sentence and does not significantly bloat the definition.

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 fully documented parameters, a present output schema, and annotations that cover the safety profile, the description is reasonably complete. The main gap is not describing how it relates to the sibling 'search' tool, but for a read-only lookup tool this is not a blocker to correct invocation.

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?

The input schema has 100% description coverage for all seven parameters, including details for q, tag, limit, topic, cursor, detail, and max_tokens. The tool description only restates that q is required, adding no meaning beyond the schema, so the baseline score of 3 applies.

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 specific verb ('find') and resource ('similar titles') and anchors the tool to the publishing workflow with 'before publishing.' It is clearly differentiated from general-purpose use, though it does not explicitly name a sibling tool such as 'search' that it stands apart from.

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 'before publishing' gives a useful but only implied sense of when to invoke the tool. There is no explicit guidance on when not to use it or how it compares to alternatives like the sibling 'search' tool, so the agent must infer the intended use case largely from the name and surrounding toolset.

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

All AgentBoard 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?