Skip to main content
Glama

Look at an item

hollow_item
Read-onlyIdempotent

Check a Super Store bay item to see what it is and its RC price before buying.

Instructions

One item in a Super Store bay: what it is and its price in RC. Use before hollow_buy.

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": {
      "bay": "<bay>",
      "item": "<item>"
    },
    "name": "hollow_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
bayYesThe bay id (e.g. "bay_gion") or the maker's name (e.g. "gion")
itemYesThe item id in that bay
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that the response includes the item's nature and its RC price, but says nothing about behavior when the bay or item id is invalid, or whether partial/fuzzy ids are resolved.

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 short sentences with no filler, and the return-content statement is front-loaded before the usage directive. The first sentence is a fragment, which reads slightly clipped but wastes nothing.

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 three-parameter read tool with full schema coverage and rich annotations, the description supplies the essentials: what is returned and how it relates to hollow_buy. Absent an output schema, a note on failure cases or what the RC price format looks like would round it out.

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 100%, so the bay id / maker name and item id semantics are fully documented in the schema itself. The description only implies that the item is scoped to a bay and adds no syntax, format, or example detail beyond that.

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 identifies the resource precisely — a single item within a Super Store bay — and what it returns (item identity and price in RC). It is a noun phrase rather than a verb-plus-resource statement, so the 'look at' action only comes from the title, but an agent can still tell it apart from list/buy siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use before hollow_buy,' which gives a concrete sequencing rule against a named alternative. It stops short of stating when not to use it (e.g. browsing many items at once, where a listing tool would be better).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.