Tool ki definition ke do kaam hain, aur unme se sirf ek JSON hai. Schema batati hai ki arguments ka aakaar kya hai; descriptions batate hain ki tool kis liye hai aur har argument ka arth kya hai. Schema poori tarah valid ho sakti hai aur phir bhi aisa tool bana sakti hai jise galat samay par, bhitar vishwasniya dikhti bakwaas ke saath bulaya jaye, kyunki JSON mein kahin ye nahi likha ki kaun-si cheez kya hai. Ye builder schema likhta hai aur dono pehlu jaanchta hai: banawat, aur ye ki kuchh sach mein varnit hai bhi ya nahi. Strict mode bhi theek se sambhala gaya hai: wo har property ko anivarya soochi mein maangta hai aur atirikt properties mana karta hai — aur yahi logon ko chaunkata hai, kyunki baaki schema waisi ki waisi dikhti hai.
Features
Types, descriptions aur optional band maan-samooh wale parameters
Strict mode ka "sab anivarya" niyam turant laagu, baad mein pata chalne ke bajaye
Strict mode chaalu ho to additionalProperties sahi set
Arrays ko items schema apne aap milti hai
Bina description wale parameter par warning
Ek jaise parameter names pakadta hai
Ek hi value wale enum ko constant batata hai
Sirf schema nahi, poori definition deta hai
MCP Tool Schema Builder kaise use karein
Tool ka naam rakhiye aur likhiye ki use kab use karna hai
Har parameter uske type aur description ke saath jodiye
Anivarya wale chuniye, ya strict mode chaalu kijiye
Definition apne tools array mein copy kijiye
Example
Input
"strict": true
Output
Error: strict mode requires every property to be listed as required
Strict mode mein optional properties nahi hotin: uski jagah null ki anumati dijiye.
Common errors aur troubleshooting
Strict mode reject ho raha hai. — Use sabhi properties anivarya aur additionalProperties ka false chahiye. Optional walon ko anivarya banakar null ki anumati dijiye, ya strict mode band kijiye.
Tool galat arguments ke saath bulaya jaata hai. — Aam taur par bina description wale parameters. Akele naam se arth anumaan par chhoot jaata hai, aur "id" kuchh bhi ho sakta hai.
Tool galat samay par bulaya jaata hai. — Ye tool ka description hai, schema nahi. Likhiye ki kab use karna hai aur kya lautata hai, sirf ye nahi ki kya karta hai.
Array wala parameter reject ho raha hai. — Arrays ko items schema chahiye jo bataye ki usme kya hai. Yahaan wo apne aap jud jaati hai.
Aksar pooche jaane wale sawaal
Strict mode asal mein kya badalta hai?
Wo guarantee deta hai ki arguments schema se theek-theek mel khayenge. Keemat ye hai ki har property anivarya soochi mein honi chahiye aur atirikt properties mana hain, isliye sach mein optional argument ko "anivarya par null sweekarya" ki tarah gadhna padta hai.
Parameter ka description kitna vistrit ho?
Itna ki sirf schema padhne wala bhi jaan jaye ki wahaan kya daalna hai: format, ikaiyan, value kahaan se aati hai. "Wo customer email jisse order kiya gaya" "email" se kahin zyada keemti hai.
Enum kab use karein?
Jab valid values ka samooh sach mein band aur chhota ho. Isse galat jawabon ki ek poori shreni hat jaati hai. Ek hi value wala enum isliye dikhaya jaata hai ki wo parameter nahi, constant hai.
Kya ye MCP aur API dono tools par laagu hai?
Dono mein schema JSON Schema ka wahi upsamuchchay hai. Bahari lapet thodi alag hoti hai, par input schema — jahaan galti aasaan hai — bilkul ek jaisi hai.
Achha tool description kise kahenge?
Do vaakyon mein teen baatein: wo kya karta hai, kab use uthana hai, aur kya lautata hai. Aakhri sabse zyada chhootti hai aur sabse zyada kaam aati hai, kyunki wo batati hai ki ek hi call kaafi hogi ya nahi.
Related tools
Tool Schema Checker — Definition paste kijiye aur jaaniye wo kyun reject ho rahi hai.
MCP Server Config — stdio, HTTP ya SSE ke liye MCP server entry banaiye.