Save the user's preferred news language and region. Call this after the user confirms their language and region preferences. Login is required to access this tool.
| Name | Required | Description | Default |
|---|---|---|---|
| region | Yes | Region slug, e.g. 'india', 'united-states', 'united-kingdom', 'japan' | |
| language | Yes | BCP-47 language code for news content, e.g. 'en', 'hi', 'ja' |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / region / enumAdded value: +[
+ "india",
+ "united-states",
+ "united-kingdom",
+ "japan",
+ "international"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the login requirement, a behavioral trait not in annotations. It aligns with annotations (not readOnly, not destructive) and does not contradict them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff, front-loaded with the main action. Efficient and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given full schema coverage and presence of output schema, the description adequately covers when to use (after confirmation) and prerequisites (login). No major gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description does not add additional meaning beyond what's already in the schema; it just names the parameters generally.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it saves the user's preferred news language and region, using a specific verb and resource. It distinguishes from siblings like set_user_preferences by focusing specifically on language and region.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context: call after user confirms preferences, and login is required. Does not explicitly mention when not to use or compare to alternatives, but the guidance is specific enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.