FreeDailyPro Tools

business_resume_outline

Read-onlyIdempotent

Resume outline builder

Input Schema

Name	Required	Description
`name`	Yes	Your name.
`title`	Yes	The job title you are applying for or hold.
`skills`	No
`contact`	No	Contact lines, one per line, shown under your name.
`summary`	No	Your own summary. When left out a one-line draft is written and flagged (summaryIsDraft).
`education`	No
`experience`	No	Jobs, newest first.
`includeDocx`	No	true also returns the outline as a Word file in result.docx (filename, contentType, base64).

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedNov 1, 2026

addedInput schema / properties / contact

Added value: +{
+  "description": "Contact lines, one per line, shown under your name.",
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / education

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "degree": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "school": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "years": {
+        "maxLength": 60,
+        "type": "string"
+      }
+    },
+    "required": [
+      "school",
+      "degree"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

addedInput schema / properties / experience / description
```
Added value: +"Jobs, newest first."
```

addedInput schema / properties / experience / items / properties / achievements

Added value: +{
+  "description": "Result lines for this job. Prompts are written in their place when left out.",
+  "items": {
+    "maxLength": 400,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

addedInput schema / properties / experience / items / properties / company / maxLength
```
Added value: +200
```
addedInput schema / properties / experience / items / properties / company / minLength
```
Added value: +1
```
addedInput schema / properties / experience / items / properties / role / maxLength
```
Added value: +200
```
addedInput schema / properties / experience / items / properties / role / minLength
```
Added value: +1
```

addedInput schema / properties / experience / items / properties / years / description

Added value: +"The period, such as 2022-2026 or 2021-Present. Must contain a real year and not end before it starts (422 otherwise)."

addedInput schema / properties / experience / items / properties / years / maxLength
```
Added value: +60
```
addedInput schema / properties / experience / maxItems
```
Added value: +30
```

addedInput schema / properties / includeDocx

Added value: +{
+  "description": "true also returns the outline as a Word file in result.docx (filename, contentType, base64).",
+  "type": "boolean"
+}

addedInput schema / properties / name / description
```
Added value: +"Your name."
```
addedInput schema / properties / name / maxLength
```
Added value: +200
```
addedInput schema / properties / skills / items / maxLength
```
Added value: +100
```
addedInput schema / properties / skills / items / minLength
```
Added value: +1
```
addedInput schema / properties / skills / maxItems
```
Added value: +60
```

addedInput schema / properties / summary / description

Added value: +"Your own summary. When left out a one-line draft is written and flagged (summaryIsDraft)."

addedInput schema / properties / summary / maxLength
```
Added value: +2000
```

addedInput schema / properties / title / description

Added value: +"The job title you are applying for or hold."

addedInput schema / properties / title / maxLength
```
Added value: +200
```

Changed2 schema fields changedNov 1, 2026
- addedInput schema / properties / name / minLength
```
Added value: +1
```
- addedInput schema / properties / title / minLength
```
Added value: +1
```
First observedOct 23, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing on top of that: it does not say that missing summary/skills/achievements get auto-drafted prompts, nor that the response contains a structured outline (and optionally a DOCX).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than economy — a four-word fragment with no front-loaded verb, scope, or output statement. Nothing in it earns its place beyond what the tool name already conveys.

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

Completeness2/5

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

This is an 8-parameter generative tool with no output schema, so the description must explain what comes back (an outline object, plus result.docx when includeDocx is true) and how defaults behave (summaryIsDraft flagging, placeholder prompts for missing achievements). None of that is present.

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

Parameters2/5

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

Schema description coverage is 75% and the schema itself documents name, title, contact, summary, years, achievements and includeDocx in detail. With coverage just under the 80% baseline, the description is expected to compensate but contributes zero parameter meaning; "builder" explains none of the 8 inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Resume outline builder" merely restates the tool name in slightly different words; it never states what action is performed (generate? validate? format?) or what the output artifact is. It also fails to distinguish this from close siblings such as business_blind_cv or business_cover_letter, which an agent could easily confuse with it.

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 when-to-use guidance, no prerequisites, and no mention of the alternative resume-related siblings (business_blind_cv, business_cover_letter). An agent must guess from the name alone whether this is the right tool for a resume task.

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

All FreeDailyPro Tools 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?