Skip to main content
Glama

palletdimensions.com freight reference

Read one dataset

get_dataset
Read-onlyIdempotent

Returns the verified rows of one published dataset, with their sources. Unverified rows are never returned; the result says how many were left out.

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

Input Schema

NameRequiredDescriptionDefault
idYesDataset id from list_datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses a real filtering behavior: unverified rows are excluded and the response reports how many were omitted. That is meaningful context an agent could not infer from the annotations, though return shape and size/pagination are still unstated.

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?

Two short sentences, zero filler, with the core behavior and the exclusion rule front-loaded.

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?

For a single-resource read with a fully documented parameter but no output schema, the description covers what is returned (rows plus sources) and what is filtered out. It stops short of describing response structure or result size, which matters somewhat since no output schema exists.

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% with a fully enumerated id list and a pointer to list_datasets as the source of valid ids, so the schema carries parameter meaning. The description adds only the 'published' qualifier and nothing about id semantics beyond that — baseline 3.

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?

States a specific verb and resource: returns the verified rows of one published dataset, with their sources. An agent immediately knows this is a single-dataset read, implicitly distinct from list_datasets, though no sibling is named explicitly.

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 — 'one published dataset' plus the schema's 'Dataset id from list_datasets' suggests the list-then-fetch flow. The description itself offers no when-to-use, when-not, or alternative routing.

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.

Resources