Skip to main content
Glama
Sign In

YappyKids shop

by lv.yappy
OverviewDiscussionsAdmin

get_store_info

Shop facts: company, languages and domains, currency, VAT, returns (14 days), warranty, delivery and payment information pages, contacts.

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

Input Schema

NameRequiredDescriptionDefault
langNoShop language: lv, lt, ee, pl, de, en, fr, ru. Defaults to the language of the domain the request was sent to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the categories of data returned (contacts, VAT, warranty, returns window), which is the main behavioral fact for a getter. However, it never states that this is a read-only, side-effect-free operation, nor anything about permissions, caching, or response shape.

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?

One compact sentence with no filler and the resource front-loaded as 'Shop facts'. It is arguably too terse as a fragment, but nothing is redundant.

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?

There is no output schema, so the enumeration of returned facts usefully stands in for a return-value description, and the single optional parameter is handled by the schema. The gaps are the missing read-only framing and the missing when-to-use routing, which are modest for a one-parameter getter.

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 single optional 'lang' parameter is fully documented in the schema, including the enum values and the domain-based default. The description adds nothing about language selection or localization behavior, so the baseline of 3 applies.

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 description is a noun phrase listing content ('Shop facts: company, languages and domains, currency, VAT, returns...') rather than a verb+resource statement, so the operation itself is only implied. The enumerated facts do let an agent infer this is a shop-metadata getter rather than a product or availability tool, but the boundary with get_delivery_options is blurred by the 'delivery and payment information pages' item.

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 when-to-use guidance, no exclusions, and no mention of any sibling tool. An agent must infer from the field list alone that this is the right call for shop-level metadata, and nothing warns it away from using this instead of get_delivery_options for delivery specifics.

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

All YappyKids shop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources