Skip to main content
Glama
leon-jarvis1

habitca-mcp

by leon-jarvis1
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_shop

Retrieve items from a Habitica shop. Choose from market, quest, time travelers, or seasonal shop. Default is market.

Instructions

Get items in a shop (default: market).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shopTypeNomarket

Implementation Reference

  • index.js:306-319 (registration)
    Registration of the 'get_shop' tool with its name, description, and input schema defining a shopType enum parameter.
    {
  name: "get_shop",
  description: "Get items in a shop (default: market).",
  inputSchema: {
    type: "object",
    properties: {
      shopType: {
        type: "string",
        enum: ["market", "questShop", "timeTravelersShop", "seasonalShop"],
        default: "market",
      },
    },
  },
},
  • index.js:449-450 (handler)
    Handler function that fetches shop items from the API using the shopType parameter, defaulting to 'market'.
    get_shop: async ({ shopType = "market" } = {}) =>
  json((await api("GET", `/shops/${shopType}`)).data),
  • index.js:309-318 (schema)
    Input schema for the get_shop tool, specifying a single optional 'shopType' string parameter with an enum of valid shop types.
    inputSchema: {
  type: "object",
  properties: {
    shopType: {
      type: "string",
      enum: ["market", "questShop", "timeTravelersShop", "seasonalShop"],
      default: "market",
    },
  },
},

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description should disclose behavioral traits. It fails to mention whether reading is safe (read-only), any authentication needs, rate limits, or what happens if the shop is empty. The description is silent on these aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that is front-loaded with the action and resource. No redundant words, and it efficiently communicates the core purpose.

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?

Given the tool has one parameter, no output schema, and no annotations, the description is too brief. It does not specify return structure, pagination, item types, or any edge cases (e.g., invalid shop type). The description is incomplete for effective usage.

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 coverage is 0%, so the description should compensate. It mentions the default shop type ('market'), which is already in the schema, but does not explain the meaning of each enum value (e.g., what 'timeTravelersShop' contains). Thus, it adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves items from a shop, with a default shop type of 'market'. It uses a specific verb ('Get') and resource ('items in a shop'), and the context of sibling tools (e.g., get_inventory, get_pets) helps distinguish it.

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?

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives like get_inventory or get_pets, nor does it specify prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leon-jarvis1/habitca_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server