Skip to main content
Glama

Mdexa

Get access method

get_access
Read-onlyIdempotent

How to obtain a dataset or model (Mdexa hosts no data): latest version, files and size, the first-choice way, how to apply, each with source and verification date. detail=full adds the file list (paged), API templates and application steps. Obtaining files grants no right to use them. Follow the official source; never invent download commands.

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": "get_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
slugYesDataset slug from search_datasets.
hintsNo
limitNoFile list page size (detail=full).
cursorNonext_cursor (detail=full).
detailNosummary

Output Schema

NameRequiredDescriptionDefault
recipeNo
sourcesNo
access_typeNo
license_statusNo
download_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: every field carries a source and verification date, obtaining files grants no right to use them, and the agent must follow the official source rather than invent download commands.

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?

Front-loaded with the core purpose, then mode behavior, then the legal/accuracy caveats; every sentence carries information. The opening sentence is dense and colon-chained, slightly reducing scanability.

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?

An output schema exists, so return-value detail is not required, and the description adequately covers the two detail modes plus legality and sourcing constraints. The remaining gap is the unexplained hints and lang parameters, minor for a read-only lookup tool.

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?

With 50% schema description coverage, the description compensates partially by explaining that detail=full adds a paged file list, API templates and application steps, which clarifies detail, limit and cursor. The lang and hints parameters remain unexplained in both schema and description, so semantics are not fully covered.

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 opens with a specific verb+resource: 'How to obtain a dataset or model', plus explicit scope ('Mdexa hosts no data') and what the response contains (latest version, files and size, first-choice way, how to apply). It is clearly distinguishable from retrieval siblings like get_card or get_license_evidence, though it never names them.

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?

Usage is only implied: the slug comes 'from search_datasets' in the schema, and detail=full is presented as an option, but there is no explicit statement of when to pick this tool over get_card, get_license_evidence, or request_dataset, and no exclusion conditions.

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.