Skip to main content
Glama
shopino-mcp

shopino-mcp

by sepehr071

Search the style blog

sh_blog_search
Read-onlyIdempotent

Search style blog guides and model galleries, newest first, to discover current fashion trends; leave the query empty to list recent posts.

Instructions

Search the style blog (guides and model galleries), newest first; no query = latest posts.

Use for what is in fashion; read a post with sh_blog_post(slug).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (3 posts per page).
queryNoTopic, Persian, e.g. 'مدل مانتو'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / query / maxLength
      Added value: +80
    • addedInput schema / properties / query / minLength
      Added value: +2
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • changedInput schema / properties / query / description
      Previous value: -"Topic, Persian, e.g. 'مدل مانتو' or 'ست کردن کیف و کفش'."New value: +"Topic, Persian, e.g. 'مدل مانتو'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"sh_blog_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "sh_blog_searchDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so safety is covered. The description adds genuinely new behavioral facts beyond them: results are ordered newest first and an omitted query returns the latest posts. It does not mention pagination limits or result shape, but the schema carries page size.

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?

Two short sentences with the scope and ordering stated first and the follow-up tool named last. Every clause carries information; nothing is redundant with the title or schema.

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 two-parameter read-only search with full schema coverage, annotations and no output schema, the description supplies what an agent needs: content scope, ordering, empty-query behavior and the next-step tool. Only minor gaps remain, such as whether results are paginated beyond the schema's fixed page size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining the null-query semantics ("no query = latest posts"), which the schema does not state. The page parameter's meaning is left entirely to the schema, which is acceptable given full coverage.

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 names a specific verb and resource (search the style blog) and scopes it to guides and model galleries, so the agent knows what content is covered. It also explicitly routes to the sibling sh_blog_post for reading a single item, which separates the two blog tools without opening either schema.

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?

"Use for what is in fashion" gives a clear usage context and "read a post with sh_blog_post(slug)" names the follow-up alternative. It stops short of stating when not to use it (e.g. versus the product-oriented sh_search), so the boundary with the rest of the sibling set is left implicit.

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