Skip to main content
Glama

drop_item

One drop by id with offers, curated status, platforms and history. Costs $0.01 USDC (x402).

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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, and it does disclose one meaningful trait: the call costs $0.01 USDC via x402, which an agent must know before invoking. It also enumerates the response contents, but says nothing about read-only semantics, error behavior for an unknown id, payment failure handling, or rate limits.

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?

Two compact sentences with zero filler, front-loading the identity of the resource and the returned fields before the cost note. The field list reads a bit like a comma dump, but each item conveys real information.

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

Completeness5/5

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

For a one-parameter lookup with no output schema and no annotations, the description covers the key unknowns: what it returns, that it targets a single drop, and that invocation has a monetary cost. Combined with the trivial schema, an agent has enough to call it correctly, with the id-source gap being the only minor omission.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. 'By id' at least establishes that the parameter is the drop identifier, but it adds nothing about format, case sensitivity, or where ids come from.

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 concrete resource and scope: a single drop retrieved by id, returning offers, curated status, platforms, and history. It is clearly a single-item detail lookup rather than a list, though it never explicitly contrasts itself with siblings like next_drops or upcoming_drops. The verb is only implied ('One drop by id') rather than stated outright.

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 explicit when-to-use or when-not-to-use guidance, and no mention of where an agent should obtain a valid id (presumably from next_drops or upcoming_drops). The phrase 'One drop by id' weakly implies this is the detail view after a list, but the agent must infer that entirely.

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