Skip to main content
Glama
Sign In

ATSPrep

by io.github.Devabubakar
OverviewDiscussionsAdmin

Open in ATSPrep Studio

open_in_studio
Read-onlyIdempotent

Use this when the user wants to edit their resume in an editor, apply a template, or download it as a PDF or Word file. Make a link that opens this resume in ATSPrep Studio, the free editor, so the user can fix it, pick a template and download a PDF. The text travels in the link's #fragment, which is never sent to a server.

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": {
      "resume_text": "<resume_text>"
    },
    "name": "open_in_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_textYesThe whole resume as plain text, one heading, role or bullet per line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description adds genuinely non-obvious behavior beyond them: the text travels in the link's #fragment and is 'never sent to a server', which is a meaningful privacy trait an agent should convey.

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 when-to-use trigger is front-loaded, and the sentences are short. There is mild redundancy (it restates the template/PDF/download idea twice), but nothing materially wasteful.

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 one-parameter tool with full schema coverage, annotations covering safety, and no output schema, the description supplies everything an agent needs: the trigger, the resulting link behavior, and the privacy model of the fragment.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents resume_text fully. The description references the resume but adds no format, length, or syntax detail beyond what the schema provides, so baseline 3 applies.

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 ('Make a link that opens this resume in ATSPrep Studio') and names the concrete outcomes (edit, apply template, download PDF). It clearly distinguishes itself from siblings like check_resume or tailor_resume, which analyze or rewrite rather than open an editor.

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?

It gives an explicit when-to-use trigger ('when the user wants to edit their resume in an editor, apply a template, or download it as a PDF or Word file'), which is clear context. However, it names no alternatives or exclusions, so the agent is left to infer that check_resume/tailor_resume are not this tool.

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

All ATSPrep 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