Skip to main content
Glama

Mdexa

Ask for a dataset to be added or verified

request_dataset

Ask for a dataset to be added to the Mdexa database, or a card verified, when search_datasets finds nothing or a card is unverified. Name required; official https URL and purpose optional. Merged by name and queued by demand; not a database call. Not for looking things up.

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": {
      "name": "<name>"
    },
    "name": "request_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
kindNoadd
langNoen
nameYes
hintsNo
purposeNo

Output Schema

NameRequiredDescriptionDefault
statusNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is supplied. The description adds non-obvious behavior beyond that: requests are 'Merged by name and queued by demand' and this is 'not a database call', which tells the agent the submission is deduplicated asynchronously rather than writing a row directly. It stops short of stating permission or quota requirements, and the interaction with idempotentHint=false (resubmitting the same name) is only implied by 'merged by name'.

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?

Roughly four short clauses arranged purpose-first, then trigger condition, then parameter constraints, then merge/queue behavior, then a closing exclusion. Every clause adds information and nothing is repeated verbatim from the schema or annotations.

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?

With an output schema present, the description need not explain return values, and it covers the decision logic and the asynchronous merge/queue behavior an agent needs to set expectations. The only material gap for a six-parameter tool with three enums is the unexplained lang and hints parameters and the semantics of choosing kind=verify versus add.

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 description coverage is 0%, so the description carries the full burden, and it only partially does so. It clarifies that name is required and that url ('official https') and purpose are optional, and the add/verify pair is implied by the opening sentence, but the lang (en/zh) and hints (on/off) enum parameters are entirely undocumented in both schema and description, and the distinction between the kind enum values is never explicitly stated.

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 gives a specific verb-plus-resource ('Ask for a dataset to be added to the Mdexa database, or a card verified') and then explicitly separates itself from the lookup path with 'Not for looking things up.' An agent can distinguish this request/filing tool from search_datasets without opening any schema.

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

Usage Guidelines5/5

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

It names the exact triggering conditions: 'when search_datasets finds nothing or a card is unverified', and names the sibling that handles the lookup case instead. It also states an explicit exclusion ('Not for looking things up'), so both the when and when-not are covered.

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.