Civify

Score Resume ATS Compatibility

civify_score_ats

Calculate ATS compatibility score and structural audit for a resume document (file path) or structured resume JSON without needing a job description. May consume AI credits; do not automatically retry.

Input Schema

TableJSON Schema

Name	Required	Description
`file`	No	A user-selected chat attachment supplied by the client. Never invent a download URL or file ID.
`file_url`	No	Actual HTTPS download URL supplied by the client or user. Never use a sandbox path, file ID alone or an invented URL.
`filename`	No	Original filename for base64 data, including extension (PDF, DOCX, PNG or JPG). Inferred from bytes when omitted.
`file_base64`	No	Base64 encoded content of the resume document (PDF, DOCX). Recommended for remote/cloud MCP servers.
`resume_data`	No	Civify ResumeData extracted by you or returned by Civify. Preserve all real details; never invent achievements. Use personalInfo for contact/summary and sections[].items for experience, education and skills. No parse call is required when you have this data.
`resume_text`	No	Complete resume text read from the attachment. Preferred fallback when the client cannot forward bytes. Do not summarize or invent missing content.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

removedInput schema / properties / api_key

Removed value: -{
-  "description": "Optional API key override.",
-  "type": "string"
-}

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / resume_data / description

Previous value: -"Structured resume JSON data."New value: +"Civify ResumeData extracted by you or returned by Civify. Preserve all real details; never invent achievements. Use personalInfo for contact/summary and sections[].items for experience, education and skills. No parse call is required when you have this data."

addedInput schema / properties / resume_data / properties

Added value: +{
+  "metadata": {
+    "description": "Optional renderer settings, such as templateId and primaryColor.",
+    "type": "object"
+  },
+  "personalInfo": {
+    "properties": {
+      "address": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "city": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "country": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "email": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fullName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "github": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "jobTitle": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "linkedin": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "phone": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "summary": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "website": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "sections": {
+    "items": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "items": {
+          "items": {
+            "properties": {
+              "date": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "description": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "location": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "subtitle": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "tags": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "title": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "visible": {
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "order": {
+          "type": "integer"
+        },
+        "title": {
+          "type": "string"
+        },
+        "type": {
+          "description": "experience, education, skills, or custom",
+          "type": "string"
+        },
+        "visible": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "type",
+        "items"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / resume_data / required
```
Added value: +[
+  "personalInfo",
+  "sections"
+]
```

Changed18 schema fields changedSep 24, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "resume_text"
-    ]
-  },
-  {
-    "required": [
-      "file_base64"
-    ]
-  },
-  {
-    "required": [
-      "server_file_path"
-    ]
-  },
-  {
-    "required": [
-      "resume_data"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "resume_text"
+    ]
+  },
+  {
+    "required": [
+      "file_base64"
+    ]
+  },
+  {
+    "required": [
+      "resume_data"
+    ]
+  },
+  {
+    "required": [
+      "file"
+    ]
+  },
+  {
+    "required": [
+      "file_url"
+    ]
+  }
+]

addedInput schema / properties / file

Added value: +{
+  "additionalProperties": false,
+  "description": "A user-selected chat attachment supplied by the client. Never invent a download URL or file ID.",
+  "properties": {
+    "download_url": {
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}

addedInput schema / properties / file_url

Added value: +{
+  "description": "Actual HTTPS download URL supplied by the client or user. Never use a sandbox path, file ID alone or an invented URL.",
+  "type": "string"
+}

removedInput schema / properties / filename / default
```
Removed value: -"resume.pdf"
```

changedInput schema / properties / filename / description

Previous value: -"Filename when providing base64 (e.g. 'resume.pdf')."New value: +"Original filename for base64 data, including extension (PDF, DOCX, PNG or JPG). Inferred from bytes when omitted."

changedInput schema / properties / resume_text / description

Previous value: -"Plain text or markdown content of the resume. Easiest option when chatting with an AI agent."New value: +"Complete resume text read from the attachment. Preferred fallback when the client cannot forward bytes. Do not summarize or invent missing content."

addedInput schema / properties / resume_text / minLength
```
Added value: +1
```

removedInput schema / properties / server_file_path

Removed value: -{
-  "description": "Local file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'resume_text' or 'file_base64' instead.",
-  "type": "string"
-}

removedOutput schema / properties / data / description

Removed value: -"ATS score details containing overall, keywordMatch, skillsMatch, missingKeywords, and suggestions"

removedOutput schema / properties / data / type
```
Removed value: -"object"
```

removedOutput schema / properties / keywordMatch

Removed value: -{
-  "description": "Keyword density and match score (0-100)",
-  "type": "number"
-}

removedOutput schema / properties / message

Removed value: -{
-  "description": "Status message",
-  "type": "string"
-}

removedOutput schema / properties / missingKeywords

Removed value: -{
-  "description": "Important keywords missing from the resume",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / overall

Removed value: -{
-  "description": "Overall ATS match score (0-100)",
-  "type": "number"
-}

removedOutput schema / properties / skillsMatch

Removed value: -{
-  "description": "Skills section alignment score (0-100)",
-  "type": "number"
-}

removedOutput schema / properties / success

Removed value: -{
-  "description": "Operation success status",
-  "type": "boolean"
-}

removedOutput schema / properties / suggestions

Removed value: -{
-  "description": "Actionable recommendations to improve ATS compatibility",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / required
```
Added value: +[
+  "data"
+]
```

Changed3 schema fields changedSep 15, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "resume_text"
-    ]
-  },
-  {
-    "required": [
-      "file_base64"
-    ]
-  },
-  {
-    "required": [
-      "file_path"
-    ]
-  },
-  {
-    "required": [
-      "resume_data"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "resume_text"
+    ]
+  },
+  {
+    "required": [
+      "file_base64"
+    ]
+  },
+  {
+    "required": [
+      "server_file_path"
+    ]
+  },
+  {
+    "required": [
+      "resume_data"
+    ]
+  }
+]

removedInput schema / properties / file_path

Removed value: -{
-  "description": "Local file path on the MCP server machine. Do NOT use for remote cloud servers; use 'resume_text' or 'file_base64' instead.",
-  "type": "string"
-}

addedInput schema / properties / server_file_path

Added value: +{
+  "description": "Local file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'resume_text' or 'file_base64' instead.",
+  "type": "string"
+}

First observedSep 15, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses a meaningful behavioral trait beyond the all-false annotations: 'May consume AI credits; do not automatically retry.' This warns of cost and non-idempotency, consistent with idempotentHint: false, and the 'do not retry' guidance is operationally critical. No contradiction with annotations (readOnlyHint: false aligns with an analysis operation). It omits auth/rate-limit detail, but the cost warning adds genuine value.

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?

Two sentences with no filler: the first front-loads the purpose and input modes, the second delivers the cost and retry warning. Every sentence earns its place, and the critical operational caveat is placed at the end without burying the main purpose.

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?

For a 6-parameter tool with an anyOf input contract and an existing output schema, the description plus fully-described parameters and output schema give an agent enough to select an input form and invoke correctly. The main gaps are the 'file path' phrasing that conflicts slightly with the actual parameter set, and the absence of input-preference ordering in the description (though the schema provides preferences like 'Recommended for remote/cloud MCP servers').

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 description coverage is 100%, and each parameter already carries rich, prescriptive guidance (e.g., 'Never invent a download URL or file ID,' 'Do not summarize or invent missing content,' 'Recommended for remote/cloud MCP servers'). The description adds only a coarse orientation to two input classes, which is helpful but does not exceed the baseline for a fully-documented schema. The 'file path' wording also does not map to any actual parameter name.

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 names a specific verb ('Calculate') and resource ('ATS compatibility score and structural audit') and clarifies the input domain ('resume document (file path) or structured resume JSON') and the absence of a job-description requirement. This clearly distinguishes it from siblings like civify_parse_cv and civify_tailor_cv. The phrase 'file path' is slightly loose relative to the schema's file/file_url/file_base64 parameters, but the core purpose is unambiguous.

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

Usage Guidelines3/5

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

The description conveys one usage condition — no job description needed — which implies when this scoring tool is appropriate versus tailoring tools. However, it names no sibling tools and offers no explicit when-not-to-use guidance or alternatives, leaving routing largely to inference. The schema partially compensates ('No parse call is required when you have this data' on resume_data), but the tool description itself does not.

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

All Civify tools Inspect

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

Need Help?