Skip to main content
Glama
Casius999

decroche-mcp

by Casius999

apply_act

Preview or perform one browser action on an employer ATS form. Safety rules block sensitive fields, payment pages, and login walls.

Instructions

Preview or perform ONE browser step on an employer ATS form.

SAFETY RULES enforced in code (non-negotiable):

  • classify_sensitive_field() is called BEFORE any fill().

  • is_payment_url() blocks the step if the URL is a payment page.

  • is_login_context() blocks the step if a login wall is detected.

  • confirm=False (default) returns a preview with requires_confirm=True. Only confirm=True actually performs the step.

  • NEVER auto-fills passwords, card numbers, CVC/CVV, IBAN, SSN, 2FA.

apply-at-source: use only on employer ATS pages, never on LinkedIn/Indeed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYes"navigate" | "click" | "fill"
paramsYesStep params dict: navigate → {url: str} click → {selector: str} or {role: str, name: str} fill → {field: str, value: str, label: str=""}
confirmNoFalse → preview only; True → perform (playwright required).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYes
targetNo
would_doYes
blockedNo
block_reasonNo
requires_confirmNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses safety rules enforced in code (sensitive field classification, payment page blocking, login wall detection) and explains the confirm/preview behavior. Does not describe return format but covers critical behavioral traits.

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 well-structured with a one-line purpose, bulleted safety rules, and parameter clarification. It is appropriately sized and front-loaded. Could be slightly more concise but no wasted sentences.

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 the tool's complexity (3 params, nested objects, output schema), the description covers core functionality, safety, and domain restrictions. It does not detail return values, but an output schema exists. Adequate for the context.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by enumerating intent-params combinations (navigate, click, fill) with examples and explaining the confirm parameter in detail beyond 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 'Preview or perform ONE browser step on an employer ATS form' with a specific verb and resource. It distinguishes from siblings by restricting to employer ATS pages and excluding LinkedIn/Indeed.

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?

Explicit guidance is provided: 'use only on employer ATS pages, never on LinkedIn/Indeed.' The confirm parameter behavior is explained (preview vs. perform). No explicit alternatives among sibling tools, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Casius999/decroche-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server