Returns configured handwritten-card products with identifiers, descriptions, images and item availability. Catalog visibility does not establish that ordering is enabled.
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "anyOf": [
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "available": {
- "type": "boolean"
- },
- "currency": {
- "const": "USD"
- },
- "description": {
- "type": "string"
- },
- "id": {
- "minLength": 1,
- "type": "string"
- },
- "imageUrl": {
- "format": "uri",
- "type": "string"
- },
- "name": {
- "type": "string"
- },
- "options": {
- "additionalProperties": false,
- "properties": {
- "combinedCharacterLimit": {
- "minimum": 0,
- "type": "integer"
- },
- "handwritingStyles": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "id": {
- "minLength": 1,
- "type": "string"
- },
- "imageUrl": {
- "format": "uri",
- "type": "string"
- },
- "label": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "label",
- "imageUrl"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "maxMessageLength": {
- "minimum": 0,
- "type": "integer"
- },
- "maxWishesLength": {
- "minimum": 0,
- "type": "integer"
- },
- "previewKind": {
- "const": "design_and_style_samples"
- },
- "size": {
- "type": "string"
- }
- },
- "required": [
- "handwritingStyles",
- "maxMessageLength",
- "maxWishesLength",
- "combinedCharacterLimit",
- "size",
- "previewKind"
- ],
- "type": "object"
- },
- "provider": {
- "const": "handwrytten"
- },
- "requiresDocument": {
- "const": false
- },
- "service": {
- "const": "handwritten"
- }
- },
- "required": [
- "id",
- "name",
- "description",
- "provider",
- "service",
- "imageUrl",
- "currency",
- "available",
- "requiresDocument",
- "options"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "data"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "minLength": 1,
- "type": "string"
- },
- "details": {
- "additionalProperties": false,
- "properties": {
- "addressRole": {
- "enum": [
- "recipient",
- "sender"
- ]
- },
- "canSendAsEntered": {
- "type": "boolean"
- }
- },
- "required": [
- "addressRole",
- "canSendAsEntered"
- ],
- "type": "object"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ],
- "type": "object"
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- }
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "available": {
+ "type": "boolean"
+ },
+ "currency": {
+ "const": "USD"
+ },
+ "description": {
+ "type": "string"
+ },
+ "id": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "imageUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "options": {
+ "additionalProperties": false,
+ "properties": {
+ "combinedCharacterLimit": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "handwritingStyles": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "imageUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "label": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "label",
+ "imageUrl"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "maxMessageLength": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "maxWishesLength": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "previewKind": {
+ "const": "design_and_style_samples"
+ },
+ "size": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "handwritingStyles",
+ "maxMessageLength",
+ "maxWishesLength",
+ "combinedCharacterLimit",
+ "size",
+ "previewKind"
+ ],
+ "type": "object"
+ },
+ "provider": {
+ "const": "handwrytten"
+ },
+ "requiresDocument": {
+ "const": false
+ },
+ "service": {
+ "const": "handwritten"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "description",
+ "provider",
+ "service",
+ "imageUrl",
+ "currency",
+ "available",
+ "requiresDocument",
+ "options"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "data"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "details": {
+ "additionalProperties": false,
+ "properties": {
+ "addressRole": {
+ "enum": [
+ "recipient",
+ "sender"
+ ]
+ },
+ "canSendAsEntered": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "addressRole",
+ "canSendAsEntered"
+ ],
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior Kus. The description adds a meaningful semantic warning: a visible catalog item may not be orderable. This is non-obvious context that helps an agent avoid falsely assuming that product presence implies checkout eligibility.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core return statement is front-loaded, and the crucial ordering caveat is placed second for emphasis without bloating the description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with rich annotations, the description provides enough to invoke it correctly: the parameter is implicit in 'handwritten-card products', output contents are listed, and a behavior trap is flagged. No output schema exists, so the listed return fields partially compensate, though response format details are absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description does not explicitly explain the 'service' parameter, but the parameter is a single enum with only one value ('handwritten') and the description's 'handwritten-card products' phrase effectively maps to it. The description still does not fully compensate for the lack of schema-level parameter documentation, so a 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Returns') and resource ('configured handwritten-card products'), then enumerates the returned contents: identifiers, descriptions, images, item availability. This cleanly separates it from sibling tools like orders or checkout, which deal with ordering rather than catalog browsing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for product discovery by stating what it returns. The caution that catalog visibility does not establish ordering availability is a helpful guardrail, but it does not explicitly say when to prefer this tool over siblings such as postedly_quote or postedly_services, nor does it list exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.