Selenios

Reorder application form fields

reorder_screening_form_fields

Idempotent

Set the order in which the candidate sees the fields of a job position's application form. fieldNames lists every field key of the form (configuration.formSchema.properties) exactly once, in the new order: the whole order, not only the fields that moved. A list that omits a field, repeats one or names one the form does not have is rejected, and the error says which. It changes presentation only, not scoring.

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": {
      "jobDescriptionId": "<jobDescriptionId>",
      "fieldNames": "<fieldNames>"
    },
    "name": "reorder_screening_form_fields"
  }
}

Input Schema

Name	Required	Description	Default
`fieldNames`	Yes	Every schema key of the form, exactly once, in the order the candidate should see them
`jobDescriptionId`	Yes	The job position ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive mutation. The description adds useful behavior beyond that: it changes presentation only and does not affect scoring, and it explains validation failures and error reporting. It does not describe authorization requirements or response format, but the important behavioral effects are disclosed.

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?

The description is compact and front-loaded: it states the effect first, then precise input requirements, then validation behavior. Every sentence contributes useful information without repetition or filler.

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

Completeness5/5

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

For a two-parameter mutation with full schema coverage, annotations, and no output schema, the description provides everything needed to invoke the tool correctly. It covers the operation's effect, input completeness requirements, and rejection behavior while clarifying that scoring is unaffected.

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%, so both parameters are already documented by the schema. The description still adds meaning by clarifying that `fieldNames` represents the complete final order rather than only moved fields, points to `configuration.formSchema.properties`, and explains rejection of missing, repeated, or unknown keys. This meaningfully extends 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 states a specific verb and resource: it sets the order in which candidates see application form fields for a job position. It is clearly distinct from sibling tools like add_screening_form_field, remove_screening_form_field, and update_screening_form_field. An agent can identify the intended operation without inspecting the schema.

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?

The description explains the key usage condition: `fieldNames` must contain the whole order, not only moved fields, and must list every form field exactly once. It also states that invalid lists are rejected. It does not explicitly name alternative tools or when not to use this one, but the reorder-specific semantics are clear.

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

All Selenios tools Inspect

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

Need Help?