Skip to main content
Glama

Values card sort

values_card_sort

Guides people unsure of their values through a card sort, returning value cards and step-by-step instructions before saving the results.

Instructions

For people unsure of their values. Returns the value cards and the steps of the sort (after the Personal Values Card Sort, Miller et al. 2001). Walk them through it, then call save_values.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully implies a read-only retrieval ('Returns the value cards and the steps') and discloses a required workflow dependency on save_values, plus the source methodology. However, it doesn't say whether the tool persists any state or session, whether the returned steps must be presented in order, or roughly what the return payload looks like for a tool with no output schema.

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 short sentences with no filler, and the citation is compactly parenthesized. Front-loading is slightly off: the audience qualifier precedes the actual behavior, so an agent skimming the first clause doesn't immediately learn what the tool returns.

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 zero-parameter, annotation-free tool with no output schema, the description covers what is returned (cards and sort steps) and the next step in the flow. The remaining gap is the shape of the returned data, which the agent must discover at call time since no output schema exists.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the schema cannot be under-served. Baseline 4 applies; nothing in the description conflicts with the empty input schema.

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?

The description names the resource precisely: it returns value cards plus the steps of a card sort, attributed to a specific published method (Miller et al. 2001). It doesn't lead with a verb+resource construction, opening instead with an audience qualifier ('For people unsure of their values'), but the second sentence makes the output unambiguous enough to distinguish it from sibling tools like save_values or get_method.

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?

It states the applicability condition ('For people unsure of their values'), which is a real when-to-use signal, and it gives an explicit follow-up action ('Walk them through it, then call save_values'), which tells the agent this tool is the entry point of a two-step flow. What's missing is a when-not case, e.g. what to do for users who already know their values.

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