IE Student MCP Free

Overview Schema Source Related Servers Discussions Admin

careers_materials

Read-onlyIdempotent

Access and review existing application documents and resume books. List views provide item IDs for detailed viewing; downloads are handled separately.

Instructions

Read existing application documents or résumé books. Detail views require an item_id returned by their list. Downloads use careers_download; no uploads or book registrations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "careers_materials"
  }
}

Input Schema

Name	Required	Default
`view`	No	documents
`limit`	No
`offset`	No
`item_id`	No

Output Schema

Name	Required	Default
`ok`	No
`data`	No
`error`	No
`message`	No
`service`	No	local
`warnings`	No
`truncated`	No
`next_action`	No
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so the description adds value by revealing the item_id dependency for detail views and the boundary that downloads are handled elsewhere. It also reinforces the read-only nature, consistent with annotations. It does not need to re-state safety traits the annotations already provide.

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?

Three short, purposeful sentences: purpose, detail-view requirement, and routing/exclusions. Information is front-loaded, and every sentence earns its place without redundancy.

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?

The tool has an output schema, so return values don't need description. The description covers how to list, how to get details, and where downloads belong. Given the read-only annotations and simple parameter set, nothing important is missing for correct invocation.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates for the most important parameter relationships: it maps view to document/résumé-book lists and details, and explains that item_id must come from a preceding list call. It does not explain limit/offset, but those are conventional pagination parameters. The enum values are self-explanatory once the description clarifies singular vs. plural.

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 opens with a specific verb and resource: 'Read existing application documents or résumé books.' This clearly distinguishes careers_materials from sibling tools like careers_jobs and careers_download. It also specifies that detail views require an item_id from a list, making the tool's scope unambiguous.

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

Usage Guidelines5/5

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

The description explicitly routes downloads to careers_download ('Downloads use careers_download') and states what the tool does not do ('no uploads or book registrations'). It also explains the list-then-detail workflow: 'Detail views require an item_id returned by their list.' This gives clear when-to-use and when-not-to-use guidance.

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

Deploy Server