Skip to main content
Glama

Factorial ATS Ops Control Plane

by app.vercel.ats-ops-control-plane-gateway

create_webhook_subscription

Create a Factorial API webhook subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true to run this live change. Ignored when dry_run=true.
dry_runNoPreview the action without sending it.
body_jsonNoJSON request body for documented write operations.
query_jsonNoAdditional documented query parameters, including bracketed filter keys.
path_paramsNoValues for path placeholders such as {id} in a write operation.
headers_jsonNoAdditional request headers for endpoints that require vendor-specific headers.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only implies a write operation ('create') but does not mention that this is a live change requiring confirmation, potential side effects, permissions, or that it follows a dry_run/confirm pattern. This is minimal disclosure.

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 a single, front-loaded sentence with no filler words. It efficiently states the core purpose, and every word earns its place.

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

Completeness1/5

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

The tool has 6 parameters, nested objects, no output schema, and no annotations, yet the description is only one sentence. It fails to explain what a webhook subscription is, when to create one, what the return value looks like, or any operational context, making it severely incomplete.

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?

The schema descriptions cover 100% of parameters, so the baseline of 3 is appropriate. The tool description adds no parameter-specific meaning beyond what the schema already provides.

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 uses the specific verb 'create' and the resource 'Factorial API webhook subscription', clearly distinguishing it from sibling tools like update_webhook_subscription, delete_webhook_subscription, and get_webhook_subscription. It unambiguously states the operation and target.

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

Usage Guidelines1/5

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

The description gives no guidance on when to use this tool, prerequisites, or how it relates to alternatives. It does not mention when to prefer create over update, or any conditions required before creating a subscription.

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

All Factorial ATS Ops Control Plane toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation5/5

Each get/list tool targets a distinct entity (answers, applications, candidates, etc.), and the generic api_request is clearly an escape hatch for undocumented endpoints rather than an overlapping tool. The singular/plural lists are unambiguous.

Naming Consistency4/5

Tools predominantly follow a consistent verb_noun snake_case pattern (create_x, get_x, list_xs, update_x, delete_x). Two outliers exist: api_request (noun_noun) and get_control_plane_capabilities (not a resource CRUD), but they are minor.

Tool Count2/5

At 39 tools, the server is heavily over-populated. Nearly every entity has both a get and list tool, and many CRUD combinations exist, but the count exceeds what is typically needed for an MCP server and could overwhelm agents.

Completeness4/5

The read surface is comprehensive with get/list for 13 entities, and write coverage for core resources (candidates, applications, feedback, job postings, webhooks). Missing delete operations and some create/update limits are acceptable for an ops control plane, though a direct update_application_phase would fill a gap.

Resources