Skip to main content
Glama

Mdexa

Find similar datasets

find_similar_datasets
Read-onlyIdempotent

Up to five similar datasets by shared tags, domains, systems and content types, each with a score and reasons. For alternatives or companions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "find_similar_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesDataset slug from search_datasets.
hintsNo
limitNo

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs supplementary context. It discloses the result cardinality and the scoring rationale, but the stated 'up to five' conflicts with the limit parameter's maximum of 10, and nothing is said about how hints alters behavior.

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?

Two compact sentences with the core capability front-loaded and no filler. Brevity is appropriate, though the second fragment ('For alternatives or companions') is too terse to carry real information.

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?

An output schema exists, so the description need not explain the score/reasons payload, and the annotations cover safety. However, for a physics-adjacent lookup tool with an undocumented hints mode and a cardinality claim that contradicts the schema, the description leaves an agent guessing on two of three parameters.

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 coverage is only 33%: only slug is documented, while limit and the on/off hints enum are unexplained. The description adds no meaning to either — it never mentions hints and its 'up to five' phrasing muddies rather than clarifies the limit parameter's 1-10 range.

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 names a specific resource (similar datasets) and states the basis of similarity (shared tags, domains, systems and content types), plus the result shape (score and reasons). It is clearly distinguishable from search_datasets, though the verb is implied by the name rather than stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trailing clause 'For alternatives or companions' gestures at intent but gives no condition for choosing this tool over search_datasets or list_facets. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.