Skip to main content
Glama

BRAINIAC Recruitment Operations

Structure a job description

recruitment-operations_job-description-structure
Read-onlyIdempotent

Read Title, Requirement, and Responsibility lines into explicit requirements. Unlabeled prose is not turned into a requirement, and a requirement counts toward a score only when it is marked required. Price $0.03 USDC. POST /api/v1/recruitment-operations/job-description-structure. An unpaid call returns the x402 payment terms and does not run.

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": "recruitment-operations_job-description-structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNotitle, string, length 1 to 200. Optional.
jobTextNojobText, string, length 1 to 20000. Optional.
requirementsNorequirements, array. Optional.

Output Schema

NameRequiredDescriptionDefault
titleNotitle. String.
issuesNoissues. Array.
statusNostatus. String.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
requirementsNorequirements. Array.
hiringDecisionNohiringDecision. Boolean.
requirementCountNorequirementCount. Number.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the bar is lower. The description nonetheless adds real value: unlabeled prose is ignored, only items marked 'required' count toward a score, and a call costs $0.03 USDC with unpaid calls returning x402 payment terms and not executing. The POST+payment framing does not contradict readOnlyHint because nothing is mutated, though it could have been stated more explicitly.

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?

Front-loaded with the transformation and its key business rules before the pricing and endpoint boilerplate. Every sentence carries information, though the raw endpoint path is filler for an agent that already has the tool bound.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to supply the parsing and payment semantics, which it does. All three parameters are optional, and the description gives enough rule context for an agent to call it correctly on a first attempt.

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% with enum values (kind, strength) fully documented, so the schema carries the burden. The description only loosely maps 'Title, Requirement, and Responsibility lines' onto title/jobText/requirements and does not explain how an explicit requirements array interacts with the prose jobText.

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 first sentence states a specific transformation: read Title/Requirement/Responsibility lines into explicit requirements, which goes beyond the title 'Structure a job description'. It's clear what the tool does, though it never contrasts itself with siblings like resume-data-extract, so the agent must infer the boundary.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. Usage is only implied by the parsing rules (input must contain labeled lines), leaving the agent to guess whether this or resume-data-extract is the right call for a given blob of text.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources