tie-mcp-server

create_checker_option

Creates checker options for a given profile and checker, accepting codename, value, and valueType for each option.

Instructions

Create checker options related to a profile and checker. Note: profileId selects a configuration profile (a lens, not a container). If the user has not specified a profile, call get_preferred_profile (or get_preferences) and use preferredProfileId — do not assume profile 1.

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": {
      "profileId": "<profileId>",
      "checkerId": "<checkerId>",
      "body": "<body>"
    },
    "name": "create_checker_option"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Validates the POST /profiles/:profileId/checkers/:checkerId/checker-options request
`checkerId`	Yes	Path parameter: checkerId
`profileId`	Yes	Path parameter: profileId

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It explains that profileId is a lens, but does not disclose mutability, side effects, or auth requirements. Adequate but not comprehensive.

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?

Two sentences, immediate action verb, no filler. The usage guidance is efficiently included without extra words.

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?

Given no output schema and 3 required params, the description covers purpose and usage well. It could mention that body is an array of options, but the schema already conveys that structure.

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%, so the schema already describes each parameter. The description adds nuance about profileId being a lens, but doesn't add meaning for body or checkerId beyond what's in the schema.

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?

The description clearly states the verb 'Create' and the resource 'checker options', and distinguishes it from listing tools like list_checker_options. The note about profileId being a lens adds precision.

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?

Explicitly tells the agent to call get_preferred_profile or get_preferences when the user hasn't specified a profile, and warns not to assume profile 1. This is actionable guidance.

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

Deploy Server