Skip to main content
Glama
alcastaro

datosgobdo-mcp

by alcastaro

find_duplicates_resource

Read-only

Detect duplicate rows in datasets to improve data quality. Specify columns, apply filters, and get duplicate groups sorted by frequency.

Instructions

Find rows that appear more than once on the given columns (or all columns).

Returns duplicate groups sorted by frequency descending. Useful for detecting data-quality issues in payroll, census, and registry datasets. First call downloads + caches. Subsequent calls reuse the cache.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesDirect URL to the file (CKAN resource 'url' field).
formatYesFormat declared in CKAN. Accepts: csv, tsv, xlsx, json.
columnsNoColumns to check for duplication. None = all columns. Example: ['Nombre', 'Cedula'] checks for rows with same name and ID.
filtersNoSame filter syntax as filter_resource. Applied before duplicate check.
limitNoMax duplicate groups to return (1–500).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
hintNo
source_urlNo
formatNo
cacheNo
columns_checkedNo
duplicate_groups_foundNo
groups_returnedNo
total_duplicate_rowsNo
columnsNo
rowsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds caching behavior ('First call downloads + caches. Subsequent calls reuse the cache.') and sorting by frequency descending, which are valuable beyond annotations. No contradictions.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the main purpose, then adds sorting and caching. No unnecessary words.

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 output schema exists, the description covers purpose, use cases, caching, and column options. Could mention result grouping format, but sorting is covered. Adequate for a tool with 5 parameters.

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%, so the description adds limited value. It includes an example for 'columns' and cross-references 'filters' to filter_resource syntax, but baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states 'Find rows that appear more than once' and specifies columns or all columns, with sorting by frequency and use cases (payroll, census). This distinguishes it from siblings like filter_resource or detect_outliers_resource.

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 says 'Useful for detecting data-quality issues' but does not explicitly state when to use this tool vs alternatives, nor gives exclusion criteria. The caching behavior is mentioned but not as usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alcastaro/datos.gob.do-MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server