Skip to main content
Glama

Little Works

sample_before_after

Sample before/after media pairs for a trade and place (definable state change).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
placeNo
tradeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether sampling is random or deterministic, what the default sample size is, what happens with zero matches, or whether media URLs are returned. 'Sampling' implies a read, but that is inference rather than disclosure.

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 short sentence with the subject front-loaded and no filler. Its brevity is efficient, though the parenthetical adds ambiguity rather than information, so it stops short of ideal.

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?

For a 3-parameter, zero-annotation, no-output-schema tool, the description is too thin: parameter formats, default sampling behavior, and result shape are all unaddressed. An agent could guess at a call but could not predict what it gets back.

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 description coverage is 0%, so the description must compensate. It does mention two of the three parameters by name (trade, place), tying them to the sampling scope, but it adds no format, matching, or requiredness semantics, and 'limit' is never mentioned. Coverage is partial at best.

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 verb 'Sample' and the resource 'before/after media pairs' are identifiable, constrained to a trade and place. However, the parenthetical 'definable state change' is unexplained jargon, and an agent cannot tell what a 'trade' refers to (a profession? a transaction? a category?) or what a sample consists of. The purpose is nameable but not disambiguated from anything.

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 statement of when to use this tool, when not to use it, or what alternatives exist. Many sibling tools return media or entities (get_material, get_recipe, discover_search), and the description gives no cue for choosing this sampling tool over them.

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