iitkgp-erp-mcp

Overview Schema Source Related Servers Discussions Admin

get_placement_notices

Retrieve placement and internship notices from the Career Development Centre. Filter notices by keyword like company name or role.

Instructions

Get placement/internship notices from CDC. Optionally filter by keyword. Example: 'SDE', 'Google', 'internship'

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": "get_placement_notices"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states it's a read operation and mentions optional filtering, but lacks details like auth, rate limits, ordering, or pagination. Output schema exists, mitigating need for return format explanation.

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 plus an example line. No wasted words. Front-loaded with core purpose.

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?

Simple tool with one optional parameter. Description covers what the tool does and how to use the filter. Output schema exists, so return information is handled elsewhere. No gaps given tool complexity.

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?

Schema description coverage is 0%, but description adds meaning: 'Optionally filter by keyword' with examples ('SDE', 'Google', 'internship'). This clarifies the parameter's purpose beyond the schema's type and default.

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?

Description uses specific verb+resource: 'Get placement/internship notices from CDC'. Clearly distinguishes from sibling 'get_academic_notices' by specifying CDC and placement/internship nature.

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?

Provides clear context: for placement/internship notices from CDC, with optional keyword filtering. Gives example keywords. No explicit exclusion or alternatives, but context sufficiently differentiates from siblings.

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