easysociable-mcp

Get gradient

get_gradient

Read-onlyIdempotent

Retrieve a gradient's full CSS recipe by gradientId, including linear angle, color stops, and semantic token values, to apply background styles after listing gradients.

Instructions

Retrieve the full gradient CSS recipe (linear angle, color stops, and semantic token values) for a specific gradient by gradientId. Call after list_gradients to materialize background styles or decorative surfaces on cards. Alternatives: Use list_gradients to search available recipes. Read-only platform catalog lookup. Returns full gradient recipe object.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gradientId`	Yes	The unique identifier of the gradient preset (e.g. grad_warm_sunset).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Gradient preset identifier.
`css`	No	Full CSS linear-gradient declaration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "css": {
+      "description": "Full CSS linear-gradient declaration.",
+      "type": "string"
+    },
+    "id": {
+      "description": "Gradient preset identifier.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.1.16Oct 5, 2026
- addedInput schema / properties / gradientId / description
```
Added value: +"The unique identifier of the gradient preset (e.g. grad_warm_sunset)."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows the safety profile without prose. The description adds a useful behavioral framing ('Read-only platform catalog lookup') but does not go beyond the annotations in any material way, and with an output schema present, return-shape detail is not required here.

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?

Front-loaded with purpose, then sequencing, then alternatives, then a behavioral note. Slightly over-stuffed for a one-parameter lookup, and the closing 'Returns full gradient recipe object' restates the opener, but nothing is misleading or wasteful enough to penalize heavily.

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 single-id read tool with full schema coverage, annotations covering safety, and an output schema covering returns, the description covers purpose, sequencing and alternatives adequately. The only minor gap is that it does not state what happens when gradientId is unknown, though that is a low-stakes omission.

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 coverage is 100% and the single gradientId parameter already carries a format example (grad_warm_sunset). The description adds no syntax or constraint detail beyond what the schema provides, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (Retrieve) and resource (full gradient CSS recipe) scoped by gradientId, and enumerates what the recipe contains (linear angle, color stops, semantic token values). It explicitly distinguishes itself from list_gradients, so an agent can tell the two apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the sequencing rule ('Call after list_gradients') and the purpose ('to materialize background styles or decorative surfaces on cards'), then names the alternative by tool name. Both when-to-use and the sibling route are stated.

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