Skip to main content
Glama
Sign In

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

hires_create_question

Create a reusable question; options apply to select/multiselect types.

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": {
      "text": "<text>",
      "type": "<type>"
    },
    "name": "hires_create_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
typeYesFrom hires_list_question_types
optionsNoAnswer options for select/multiselect types
company_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / company_id / description
      Removed value: -"Target company ID (uses default company when omitted)"
    • changedInput schema / properties / options / description
      Previous value: -"Answer options (for select/multiselect question types)"New value: +"Answer options for select/multiselect types"
    • removedInput schema / properties / text / description
      Removed value: -"Question text"
    • changedInput schema / properties / type / description
      Previous value: -"Question type (from hires_list_question_types)"New value: +"From hires_list_question_types"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The description adds a useful behavioral constraint (options only apply to select/multiselect types) beyond the annotations. However, it does not disclose other behaviors like idempotency, permission requirements, or what happens on duplicate creation. Annotations already indicate a non-read-only operation, so the description adds some value but not extensive transparency.

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?

The description is a single sentence, front-loaded with the main action and constraint. It is appropriately concise with no wasted words, though it could include more context without becoming verbose.

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 create tool with no output schema, the description omits return behavior or success indicators. It does not mention company_id requirements or any caveats beyond the options constraint. Given the tool has four parameters and two are undocumented, the description is incomplete for a fully informed call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents options with the same note, so the description adds little for that parameter. It does not compensate for the undocumented parameters text and company_id (50% schema coverage). The type parameter's guidance to list_question_types is not repeated in the description, and no additional semantics are provided for the remaining params.

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 states a specific verb and resource ('Create a reusable question') and adds a clarifying constraint about options. It is clear but does not explicitly differentiate from other create_* tools like create_form or create_application, though the resource name makes it unambiguous.

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 provided on when to use this tool versus alternatives such as update_question or list_questions. There is no mention of exclusions, prerequisites, or scenarios where another tool is preferable.

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

All 100Hires - AI ATS & Recruitment Software 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