Skip to main content
Glama

Dataset distribution metadata

bpj_dataset_distribution_metadata
Read-onlyIdempotent

Build Dataset and DataDownload metadata with license, media type and download location.

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>",
      "download": "<download>",
      "license": "<license>",
      "media": "<media>"
    },
    "name": "bpj_dataset_distribution_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
mediaYes
licenseYes
downloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavior beyond that — it does not say what is returned, whether the URLs are validated, or how the Dataset and DataDownload fragments relate in the output.

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?

It is a single front-loaded sentence with no filler, and the resource is named first. The brevity is efficient but borders on under-specification given the tool's output is not described anywhere else.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (four required strings, no nesting) but has no output schema, so the description is the only place the return value could be characterized — and it is silent. For a metadata-builder whose entire value is the produced fragment, that is a real gap.

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 must compensate, and it only echoes three of the four parameters (license, media type, download location) without naming `name`. It provides no format constraints for the URLs, no indication of accepted media-type vocabulary (e.g., IANA values), and no ordering or nesting semantics for how the fields combine.

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 verb ("Build") and specific resources (Dataset and DataDownload metadata), which distinguishes it from the many sibling metadata builders for other schema.org types such as bpj_book_isbn_metadata or bpj_recipe_ingredient_metadata. It is clear what kind of object is being constructed, though "Build" leaves the output medium (JSON-LD snippet? record? string?) unstated.

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?

There is no guidance on when to use this tool versus the sibling metadata builders, no preconditions, and no explanation of when Dataset metadata versus DataDownload metadata applies. The agent must infer the selection criteria entirely from the tool name and its own knowledge of schema.org.

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.