Skip to main content
Glama

SizeMyFile

Filter & query data

data_query
Idempotent

Keep columns, filter rows, sort or run a bounded SQL query. Bounded processing; 32 MiB combined input per operation, at most 50 files. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "data_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: fixed resource bounds (32 MiB combined input, at most 50 files), that it queues an asynchronous run and returns an ID for tracking, and that it consumes a cloud allowance. It stops short of stating authorization requirements or what happens when limits are exceeded.

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?

Four short sentences, front-loaded with the operations, then constraints, then async behavior and cost. There is no filler; 'Uses cloud allowance' is terse but load-bearing for cost awareness.

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?

An output schema exists, so return values need not be explained, and the async run model is clear from 'returns its ID for progress and output tracking'. However, for a tool with a 0%-documented nested schema and four top-level parameters, the description leaves key operational details (idempotency_key, allow_server_fallback, output encoding, pagination) uncovered.

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% across a nested options object with limit, offset, output, deduplicate, sort, filter, and query fields, plus required artifacts and idempotency_key. The description explains only the column/filter/sort/query subset and says nothing about pagination (limit/offset up to 50000), the output format enum, or the idempotency_key requirement, leaving much of the schema meaning unstated.

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 specific verbs and resources: keep columns, filter rows, sort, or run a bounded SQL query over artifacts. An agent immediately understands this is a tabular data selection tool. It does not, however, distinguish itself from likely siblings such as data_view, data_aggregate, or log_filter.

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 implied by the operation list and by the constraints (bounded processing, cloud allowance), which hints this is the heavy/paid path, but there is no explicit when-to-use or when-not-to-use guidance and no alternatives are named. The agent must infer that data_view or data_aggregate are different choices.

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.