Mimicus

Overview Schema Source Related Servers Discussions Admin

mimicus_search

Find current design references from the seven live source indexes. A new search fetches fresh data; operationId explicitly continues a bounded RAM-only operation. Native labels and computed similarity remain distinct.

Instructions

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

Input Schema

Name	Required	Description	Default
`mood`	No
`limit`	No
`query`	No
`style`	No
`stream`	No
`purpose`	No
`awwwards`	No
`category`	No
`industry`	No
`providers`	No
`retrieval`	No
`navigation`	No
`sourceSort`	No
`technology`	No
`interaction`	No
`operationId`	No
`retentionLimit`	No
`candidateWindow`	No
`originalReferences`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.1.0Oct 22, 2026

addedInput schema / properties / awwwards

Added value: +{
+  "properties": {
+    "award": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "country": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "details": {
+      "type": "boolean"
+    },
+    "font": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "listingUrl": {
+      "format": "uri",
+      "maxLength": 2048,
+      "type": "string"
+    },
+    "tag": {
+      "maxLength": 120,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / candidateWindow

Added value: +{
+  "maximum": 200,
+  "minimum": 10,
+  "type": "integer"
+}

changedInput schema / properties / originalReferences / items / required

Previous value: -[
-  "title",
-  "url",
-  "listingUrl"
-]New value: +[
+  "url"
+]

addedInput schema / properties / retentionLimit

Added value: +{
+  "maximum": 600,
+  "minimum": 10,
+  "type": "integer"
+}

First observedv0.3.0-beta.2Oct 19, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Goes beyond the annotations: it explains why the call is non-idempotent (fresh fetch each time), discloses that operationId continues a 'bounded RAM-only operation' (ephemeral state, not persisted), and that native labels vs computed similarity are distinct in results. That is meaningful behavioral context the structured fields do not carry.

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 compact sentences, front-loaded with purpose, no filler. Some phrasing is jargon-heavy ('bounded RAM-only operation', 'native labels') that could be plainer, but it is not padded.

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?

For a tool with 19 undocumented parameters and no annotations guidance on pagination or rate limits, the description leaves too much unsaid. The output schema excuses it from explaining returns, but the input surface is barely covered.

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

Parameters2/5

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

19 parameters with 0% schema description coverage, and the description only explains operationId. Fields like retrieval, candidateWindow, retentionLimit, providers, sourceSort, and awwwards sub-fields are left entirely opaque.

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?

States a specific verb and resource ('Find current design references') and scopes it to 'the seven live source indexes', which maps to the providers enum. It is the only search tool among the siblings, so differentiation is mostly implicit, but the resource is clear.

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?

It distinguishes starting a new search ('fetch fresh data') from continuing via operationId, which is real usage guidance. However, it never says when to use this versus mimicus_preview_references, mimicus_explore_page, or mimicus_get_reference, and no prerequisites or exclusions are given.

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

Deploy Server