Skip to main content
Glama
Sign In

Creative Constraints

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Constraint

get_constraint
Read-onlyIdempotent

Fetches one specific card from Pipeworx's original creative-constraints deck by its id (e.g. "inversion_03") — returns its category, title, the constraint sentence and why it helps. Use list_constraint_categories or a draw_constraint result to find real ids.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "wildcard_05"
    },
    "name": "get_constraint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe card id, e.g. "perspective_01" or "wildcard_12".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, non-destructive, open-world, so the safety profile is covered. The description adds value beyond them by disclosing the shape of the return payload (category, title, constraint sentence, why it helps), which tells the agent this is a fixed-content lookup rather than a dynamic query.

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?

Single dense sentence for the core action plus one short sentence for id sourcing — front-loaded and zero filler. Every clause carries information an agent needs.

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?

No output schema exists, and the description compensates by listing the returned fields, so the agent knows the return shape. The only remaining gap is behavior on a nonexistent id, which is minor for a simple read-only lookup.

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 coverage is 100% and the id parameter is already documented with examples, so the baseline is 3. The description goes further by naming a concrete id ("inversion_03") and explaining the authoritative source of valid ids, adding provenance the schema cannot express.

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 (fetches) and a precisely scoped resource (one specific card from Pipeworx's original creative-constraints deck by id), including a concrete id example. It also enumerates the returned fields, so an agent knows exactly what it gets and can distinguish it from draw_constraint and list_constraint_categories.

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?

Explicitly directs the agent to list_constraint_categories or a draw_constraint result to obtain real ids, which is the main usage pitfall for an id-keyed lookup. It doesn't spell out when-not to use it or error behavior for bad ids, but the positive routing is clear and actionable.

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

All Creative Constraints toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources