Skip to main content
Glama

Search by owned items

search_by_owning
Read-onlyIdempotent

Ranks the fixed costume catalog by how many of each idea's materials are covered by the supplied household items, so ideas needing the least extra shopping rank highest. Each result includes what the idea still needs, with each still-needed item tagged buy, own, either, or make. Common household basics are assumed present in every home; the exact assumed list is returned with each call. An optional audience narrows results to who the costume is for.

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": {
      "items": "<items>"
    },
    "name": "search_by_owning"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesHousehold items the user owns, e.g. ['bedsheet', 'cardboard', 'red t-shirt']. Common household basics (scissors, tape, markers, cardboard, a white t-shirt, a bedsheet, socks, and more) are assumed present in every home; the tool returns the exact assumed list with each call.
who_forNoOptional: who the costume is for, e.g. 'toddler', 'adult', 'couple'. Narrows results to that audience when given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value on top: it discloses the ranking order, the tag vocabulary attached to each still-needed item (buy/own/either/make), and the important behavioral assumption that common household basics are treated as present. It stops short of describing result volume, pagination, or empty-result behavior.

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?

Three tight sentences: ranking rule first, then result shape and tags, then the assumption and audience caveat. Nearly every sentence earns its place, with only mild duplication of the 'assumed list is returned' claim that the schema also states.

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?

With no output schema, the description carries the return-value burden and does so: it explains the ordering, that each result shows remaining needs, and the tag taxonomy on those needs. Combined with annotations covering safety and a fully documented 2-parameter schema, an agent has everything needed to call this correctly.

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%, and the schema already documents both the items array and the assumed-basics behavior plus the who_for narrowing, so the description largely restates structured data. It confirms the ranking semantics that give 'items' meaning but adds no new syntax or format detail. Baseline 3 applies.

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 specific operation — ranking the fixed costume catalog by how much of each idea's material list is already covered by the supplied household items — and states the ranking rule (least extra shopping first). That is enough to separate it from get_build_guide and pick_costume, though it never names those siblings explicitly.

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 framing ('so ideas needing the least extra shopping rank highest') makes the intended use case reasonably clear, and the optional audience parameter's narrowing effect is stated. However, there is no explicit when-to-use versus when-to-use-a-sibling guidance and no exclusions, so routing between this and pick_costume is left to inference.

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.