Skip to main content
Glama

Steer intent

steer_intent

Computes a local steering directive that preserves kernel constraints and replaces domain clichés with a cross-domain anchor to guide output away from stock patterns.

Instructions

Compute a local quotient-manifold steering directive (<=35 tokens) that preserves the kernel and replaces average clichés with a cross-domain anchor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "kernel_constraints": "<kernel_constraints>"
    },
    "name": "steer_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
alphaNo0.0 = same, 0.5 = near, 1.0 = far. Default 0.5.
domainYescoding_architecture, music_composition, visual_design, creative_writing, cultural_discovery, or a short alias such as coding, music, design, writing, film, book.
exclude_tagsNoPatterns that must be banned in addition to the domain's mode ideals.
kernel_constraintsYesImmutable functional requirements that must survive the steering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. However, the description does not explain what side effects occur despite being non-read-only, nor does it clarify what 'preserves the kernel' means operationally or how the directive is produced. It adds only the token limit and a high-level transformation goal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, but the density of undefined jargon ('quotient-manifold', 'kernel', 'average clichés') makes it less structurally clear than a concise definition should be. The token cap is front-loaded usefully, but the sentence could be split or unpacked.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-read-only tool with no output schema, the description should clarify the return shape and side effects. It states a token limit but not the directive's structure, and it leaves the non-read-only annotation unexplained. The schema covers parameters, but the overall behavior remains under-described.

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 description coverage is 100%, so all four parameters are already documented in the input schema. The description references 'kernel' and 'cross-domain anchor' in abstract terms but adds no concrete parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Compute') and resource ('steering directive'), but the core noun phrase 'local quotient-manifold steering directive' is highly specialized jargon that an agent may not map to a concrete operation. It does not differentiate this tool from siblings commit_output or diversity_telemetry.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only usage-like detail is the <=35 token output cap, which is a constraint rather than selection guidance.

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

Deploy Server

Other Tools