get_origami_stepsReturns all illustrated folding instructions and the Finish note for a model slug, identifier or unambiguous name.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Public model slug, identifier or unambiguous model name. |
| Name | Required | Description | Default |
|---|---|---|---|
| view | Yes | ||
| model | Yes | ||
| start | Yes | ||
| steps | Yes | ||
| finish | Yes | ||
| startDiagramUrl | Yes | 800-pixel-wide PNG on a white background. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "finish": {
+ "type": "string"
+ },
+ "model": {
+ "additionalProperties": false,
+ "properties": {
+ "ages": {
+ "items": {
+ "type": "number"
+ },
+ "type": "array"
+ },
+ "airplane": {
+ "type": "boolean"
+ },
+ "category": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "difficulty": {
+ "type": "string"
+ },
+ "estimatedMinutes": {
+ "type": "integer"
+ },
+ "family": {
+ "type": "string"
+ },
+ "familyName": {
+ "type": "string"
+ },
+ "glue": {
+ "type": "boolean"
+ },
+ "holidayFacts": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "age": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "idea": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "tools": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "age",
+ "idea",
+ "tools"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "id": {
+ "type": "string"
+ },
+ "materials": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "occasions": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "pageUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "paper": {
+ "type": "string"
+ },
+ "paperGuidance": {
+ "additionalProperties": false,
+ "properties": {
+ "fromStandardSheet": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "dimensionsMm": {
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 2,
+ "minItems": 2,
+ "type": "array"
+ },
+ "largestSquareMm": {
+ "type": "number"
+ },
+ "name": {
+ "type": "string"
+ },
+ "pageUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "text": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "dimensionsMm",
+ "largestSquareMm",
+ "text",
+ "pageUrl"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "guideUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "paperSizeMm": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 2,
+ "minItems": 2,
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "paperType": {
+ "type": "string"
+ },
+ "recommended": {
+ "type": "string"
+ },
+ "shape": {
+ "enum": [
+ "square",
+ "rectangle",
+ "other"
+ ]
+ },
+ "typeUrl": {
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "recommended",
+ "shape",
+ "paperSizeMm",
+ "paperType",
+ "guideUrl",
+ "typeUrl",
+ "fromStandardSheet"
+ ],
+ "type": "object"
+ },
+ "paperSizeMm": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 2,
+ "minItems": 2,
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "posterUrl": {
+ "description": "WebP picture of the finished model.",
+ "format": "uri",
+ "pattern": "\\.webp$",
+ "type": "string"
+ },
+ "printUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "route": {
+ "type": "string"
+ },
+ "scissors": {
+ "type": "boolean"
+ },
+ "size": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "start": {
+ "type": "string"
+ },
+ "stepCount": {
+ "type": "integer"
+ },
+ "templateUrl": {
+ "anyOf": [
+ {
+ "description": "800-pixel-wide PNG on a white background.",
+ "format": "uri",
+ "pattern": "\\.png$",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "timeBasis": {
+ "type": "string"
+ },
+ "tips": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "slug",
+ "id",
+ "route",
+ "name",
+ "description",
+ "category",
+ "family",
+ "familyName",
+ "difficulty",
+ "stepCount",
+ "paper",
+ "size",
+ "materials",
+ "paperGuidance",
+ "paperSizeMm",
+ "scissors",
+ "glue",
+ "occasions",
+ "ages",
+ "holidayFacts",
+ "estimatedMinutes",
+ "timeBasis",
+ "airplane",
+ "tips",
+ "start",
+ "posterUrl",
+ "pageUrl",
+ "printUrl",
+ "templateUrl"
+ ],
+ "type": "object"
+ },
+ "start": {
+ "type": "string"
+ },
+ "startDiagramUrl": {
+ "description": "800-pixel-wide PNG on a white background.",
+ "format": "uri",
+ "pattern": "\\.png$",
+ "type": "string"
+ },
+ "steps": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "diagramUrl": {
+ "description": "800-pixel-wide PNG on a white background.",
+ "format": "uri",
+ "pattern": "\\.png$",
+ "type": "string"
+ },
+ "number": {
+ "type": "integer"
+ },
+ "parts": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "text": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "number",
+ "title",
+ "text",
+ "diagramUrl"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "view": {
+ "const": "steps"
+ }
+ },
+ "required": [
+ "view",
+ "model",
+ "start",
+ "startDiagramUrl",
+ "steps",
+ "finish"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that the response includes the Finish note alongside the steps, which is useful content context, but says nothing about behavior on ambiguous or unknown slugs, ordering, or size of the returned instruction set.
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?
A single front-loaded sentence with no filler; the resource and return contents come first and nothing is repeated.
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?
With an output schema present and annotations covering safety, the description only needs to establish purpose and scope, which it does. The remaining gap is routing guidance against the sibling tools and expected behavior for an unresolvable or ambiguous slug.
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 description coverage is 100% and the single required slug parameter is fully documented in the schema, including its accepted forms. The description merely restates 'model slug, identifier or unambiguous name', adding no format or resolution semantics beyond the schema.
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?
States a specific verb and resource — returns illustrated folding instructions plus the Finish note for a model. It is clearly a 'steps' retrieval distinct from a model-details lookup, but it never names the sibling get_origami or find_origami to make the distinction explicit.
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?
There is no when-to-use statement, no prerequisite, and no reference to the four sibling tools. An agent must infer from the resource name alone that this is the call for full step-by-step instructions rather than model metadata (get_origami) or discovery (find_origami).
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.