Skip to main content
Glama

The MW Desk Data Center API

dc_sample

Free: three example rows from each paid tool so you can see the data shape before buying credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dc_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the notable trait that this call is free and returns a bounded, small result ('three example rows'), which is meaningful behavior beyond a name. It does not state whether the call is read-only, whether it hits live data or a static snapshot, whether it has rate limits, or what the rows look like structurally, so key behavioral questions are left open.

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?

A single well-formed sentence that leads with the most decision-relevant fact ('Free') and then explains the payoff. Nothing is redundant or padded, though the fragment style ('Free:') is slightly clipped rather than descriptive.

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?

This is a simple zero-parameter tool, so the bar is low, and the description covers the essential fact of what comes back and why. However, with no output schema present, the description should say more about the return shape — whether rows are grouped by tool, what keys or fields appear, or how the three-row limit is applied — none of which is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is fully described (an empty object with additionalProperties false), so there is nothing for the description to clarify. Baseline of 4 applies; the description correctly implies no inputs are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource sampled ('three example rows from each paid tool') and the intent ('see the data shape before buying credits'), but it never supplies a verb or a precise noun for the operation — 'dc_sample' and 'sample rows' are inferred rather than stated. It does hint at the relationship with the paid siblings, which helps distinguish it, but the core action remains implicit.

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?

The phrase 'before buying credits' implies the when-to-use case (pre-purchase preview), which is genuinely useful context. It stops short of naming or excluding alternatives such as the pricing tool, and it never says when not to use this tool or what happens if you have already purchased credits, so guidance is implied rather than explicit.

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